Buildpet
Hi Tman,
Done it.
Must have been a fault in the source. It's version 869 now, and the script worked on it with flying colors. The only other thing I did differently this time, was the sequence of actions. Loaded devx first and then installed buildpet (pupmode 5 here, compiling in RAM). Great tool, it can/should reshape the way this community interacts. Instead of posting/downloading pets, one can have a script that will compile him a perfect app/proggram. Predefine "march=native" cflag, and the user will have the fastest, neatest code compiled exactly for his and only his processor. As for GUI, I'm against it for two reasons. We all will be better off if devs' time is spent on things that matter. Secondly, we noobs can learn a lot more if/when pushed to see what's going on under the hood.
Thank you.
Done it.
Must have been a fault in the source. It's version 869 now, and the script worked on it with flying colors. The only other thing I did differently this time, was the sequence of actions. Loaded devx first and then installed buildpet (pupmode 5 here, compiling in RAM). Great tool, it can/should reshape the way this community interacts. Instead of posting/downloading pets, one can have a script that will compile him a perfect app/proggram. Predefine "march=native" cflag, and the user will have the fastest, neatest code compiled exactly for his and only his processor. As for GUI, I'm against it for two reasons. We all will be better off if devs' time is spent on things that matter. Secondly, we noobs can learn a lot more if/when pushed to see what's going on under the hood.
Thank you.
- Attachments
-
- success.jpeg
- (13.82 KiB) Downloaded 1417 times
I find it very puzzling that the modified script still gave you errors, whereas it work okay for me. But at least it works for you now. When I gave you advice about, modifying /usr/bin/buildpet to keep the directory structures, I tried it myself will the Jwm build, and it would give me problems after the second time I tried to compile it.
So my advice now, is allow the directory structures to be deleted... in other words, keep it the way it was before.
If you really want to see the directory structure inside a pet, you can use the rox right-click option to "extract pet", or you can try my alternative: pet2dir_ROXrightclick-1.1.pet
When you want to learn, then read the scripts and try to compile manually. After you understand how to compile and build pets, make your own scripts and use the terminal to debug.
After your script is finalized, use the gui to save time .
So my advice now, is allow the directory structures to be deleted... in other words, keep it the way it was before.
If you really want to see the directory structure inside a pet, you can use the rox right-click option to "extract pet", or you can try my alternative: pet2dir_ROXrightclick-1.1.pet
My opinion is; first try the gui if you don't know what you are doing.anikin wrote:As for GUI, I'm against it for two reasons. We all will be better off if devs' time is spent on things that matter. Secondly, we noobs can learn a lot more if/when pushed to see what's going on under the hood.
When you want to learn, then read the scripts and try to compile manually. After you understand how to compile and build pets, make your own scripts and use the terminal to debug.
After your script is finalized, use the gui to save time .
Hi Tman,
I was somewhat slow witted in understanding how to use your pet, but then I tried it to make a pet of the latest JWM version (869 test) and it was really smooth and easy and its size is only 74K (v 845 test - 96K).
Also, anikin's screen shot (two posts above) shows a jwm cog which suggests, to me, it is compiled machine code; whereas mine looks like a pet and installed as a pet?
My regards and thanks
I use Precise 5.6 with JWM and ROX from a Multi-session-Live-CD and have made an sfs from your pet as that will suit my personal needs best.
I was somewhat slow witted in understanding how to use your pet, but then I tried it to make a pet of the latest JWM version (869 test) and it was really smooth and easy and its size is only 74K (v 845 test - 96K).
Also, anikin's screen shot (two posts above) shows a jwm cog which suggests, to me, it is compiled machine code; whereas mine looks like a pet and installed as a pet?
My regards and thanks
I use Precise 5.6 with JWM and ROX from a Multi-session-Live-CD and have made an sfs from your pet as that will suit my personal needs best.
it just occured to me the problem with the jwm buildscript i made is almost certainly cos it uses which to find the 'old' jwm... it's dumb of me... jwm might not be installed.. that is off the top of my head..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Hi sc0ttman,
... and I thought, why Akita was mentioned in that script
One more thing I forgot to mention. I have removed these: from my profile. Don't they belong to individual build scripts? They also show up in the compile log
... and I thought, why Akita was mentioned in that script
One more thing I forgot to mention. I have removed these:
Code: Select all
--disable-static --enable-shared --disable-debug --without-pic"
Code: Select all
configure: WARNING: unrecognized options: --disable-static, --enable-shared, --without-pic
Tman, Your GUI approach (@Sc0ttman) is going to revolutionize how things build in PUPs for both newbies and experienced alike! Users of the toolset will spend less time figuring things out and more time actually expanding their PUPPY experience and making things which move forward in use in this community.
Thanks as you move the needle in this community. Great...great....grrreeatt!
Thanks as you move the needle in this community. Great...great....grrreeatt!
/usr/bin/buildpet
line 107, haven't looked any further yet.
line 107, haven't looked any further yet.
Code: Select all
#tar up the source if a dir
if [ -d $WORK_DIR/$PKG_NAME-$PKG_VER ] && [ ! -f $WORK_DIR/$PKG_NAME-$PKG_VER.tar.bz2 ];then
cd $WORK_DIR
tar -cjf $PKG_NAME-$PKG_VER.tar.bz2 $PKG_NAME-$PKG_VER
cd $BUILD_DIR
fi
yeah the buildpet script needs to be updated, as Joe moved the source, and now uses a different archive format... the re-write should take about 2 mins... at work right now tho...Jasper wrote:Hi amigo,
Your src2pkg compiled the latest jwm versions 885 and 886.
My regards and thanks
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
2016 : Do it Yourself being the rule
2016 : Do it Yourself being the rule, users must learn and manage compilation.
Puppy-builders build, but raw Puppies (standard or clone ? what is the right word to describe it ?)
Puppy-builders build, but raw Puppies (standard or clone ? what is the right word to describe it ?)