Buildpet

Message

anikin · #31 Post by **anikin** » Thu 26 Sep 2013, 02:52

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.

Tman · #32 Post by **Tman** » Thu 26 Sep 2013, 04:51

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

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.

My opinion is; first try the gui if you don't know what you are doing.
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

.

Jasper · #33 Post by **Jasper** » Thu 26 Sep 2013, 16:43

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.

sc0ttman · #34 Post by **sc0ttman** » Thu 03 Oct 2013, 18:05

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..

anikin · #35 Post by **anikin** » Thu 03 Oct 2013, 20:34

Hi sc0ttman,
... 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"

from my profile. Don't they belong to individual build scripts? They also show up in the compile log

Code: Select all

configure: WARNING: unrecognized options: --disable-static, --enable-shared, --without-pic

gcmartin · #36 Post by **gcmartin** » Fri 04 Oct 2013, 04:11

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!

bpuppy · #37 Post by **bpuppy** » Wed 15 Jan 2014, 22:03

This project is very interesting to me. Great work to you all.

We are now in January 2014, whatever happened to it? Can someone give us an update on this subject please?

Jasper · #38 Post by **Jasper** » Sun 19 Jan 2014, 12:10

Hi,

I would like to make a pet of the latest jwm v. 885, however in his ChangeLog on 4th Jan 2014 Joe wrote “Use xz instead of bz2“.

So in the jwm.bp file, in the three places where I found “bz2“ I substituted “xz

amigo · #39 Post by **amigo** » Sun 19 Jan 2014, 14:12

src2pkg -PET URL-of-source

anikin · #40 Post by **anikin** » Sun 19 Jan 2014, 14:46

/usr/bin/buildpet
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

Jasper · #41 Post by **Jasper** » Sun 26 Jan 2014, 11:24

Hi amigo,

Your src2pkg compiled the latest jwm versions 885 and 886.

My regards and thanks

sc0ttman · #42 Post by **sc0ttman** » Sun 26 Jan 2014, 11:28

Jasper wrote:Hi amigo,

Your src2pkg compiled the latest jwm versions 885 and 886.

My regards and thanks

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...

Pelo · #43 Post by **Pelo** » Wed 17 Feb 2016, 04:26

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 ?)

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Buildpet

Compiling

2016 : Do it Yourself being the rule