Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 18 Sep 2014, 01:39
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Unsorted
Compiler GUI and other packaging tools
Moderators: deshlab, Flash, GuestToo, Ian, JohnMurga, Lobster
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 12 [172 Posts]   Goto page: Previous 1, 2, 3, 4, ..., 10, 11, 12 Next
Author Message
technosaurus


Joined: 18 May 2008
Posts: 4351

PostPosted: Wed 01 Jul 2009, 21:42    Post subject:  

the problem there is with the echo command in Puppy not "echoing" the = (that is why I added the common default options that contain an equal sign) I believe the version 0.07 had similar options included (for upup). It should be fine to edit the ./configure --prefix.... line in src2all with those with an = as default options

also you can put the options (no = sign though) in a text file and pass it to src2all from the command line as the second option $2 (the third option "$3" is a directory containing a tree of extra files and the first "$1" is of course your source tarball)

if your options are common config attributes (and I suspect that they might be) I may add them to the defaults.

side note:
I wanted to add tar.lzma support but it seems that Barry configured busybox to only do lzma compression up to level 6 (7,8 and 9 require an extra config option to be set that does add some size)... it may be time to add the extra small amount of weight though since many packages are now released as tar.lzma and also because puppy is one of if not THE best distros for dialup - it would really help them out (as well as those of us who up/download a lot with slower "high speed" connections)

completely off topic:
doesn't all data travel at the same "speed" strictly speaking - light speed - wouldn't it be better to say a high rate of data transfer ... maybe not - does anyone still have one of those old modems that used a speaker/mic attached to a handset - I guess at least part of that process relies on the speed of sound

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Thu 02 Jul 2009, 02:28    Post subject:  

Regarding the old modem: There was an awesome Picture story on Toms Hardware with one of those, or maybe it was another site, or maybe it was a video I watched where he got it to work. I thought it was awesome, he did Lynx... in 800 baud... it was awful.

Anyhow, I suppose then I interpreted that correctly, I looked at src2all.

Found line:
./configure --build=i486-t2-linux-gnu --prefix=/usr $CONFOPTS

So I assume I stick everything else in and it should not vomit too much. That sounds SPLENDID.

Just make sure $confopts doesn't have = things, otherwise pass it as a config file, that JUST has the contents of what I want I guess.

Thanks! I think. I hope...
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Thu 02 Jul 2009, 02:30    Post subject:  

New question:

From the original wiki page mentioned earlier, I saw...
-build=i486-pc-linux-gnu
And in the src2all, I saw...
--build=i486-t2-linux-gnu

So... what's the difference between pc and t2? New at this part and not sure what are best options so the pets I compile are easy for the system to figure out dependencies, and are properly going to run right for other users such that they are compatible with the standard "This is how it should be done in puppy!" thing...

Thanks!
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4351

PostPosted: Thu 23 Jul 2009, 19:47    Post subject:  

my odd numbered releases have 'pc' and the even ones have 't2'
odd numbers are for upup style woof builds (still in development)
even numbers are for 4.X (possibly earlier versions too)

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4351

PostPosted: Sun 23 Aug 2009, 20:55    Post subject:  

This time I added a bunch of personally selected size optimizations into the build scripts, also testing zip and xz formats and removed 2petnsfs since it was only useful for manual builds.

usage is the same but you should get smaller packages by 10-40%

once this is fully debugged I would recommend setting up a repository for config files similar to slack builds (this would open the role of package maintainer to a much wider group)
pcompile-0.1.0.pet
Description 
pet

 Download 
Filename  pcompile-0.1.0.pet 
Filesize  4.07 KB 
Downloaded  657 Time(s) 

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Mon 24 Aug 2009, 14:03    Post subject:  

So, I tested out Pcompile 0.1.0, found a minor issue - in src2all, the following line:
Code:
CFLAGS=" -pipe -combine -Os -ffunction-sections -fdata-sections -momit-leaf-frame-pointer -fomit-frame-pointer -march=i486 -mtune=i486 " CXXFLAGS=" -pipe -combine -Os -ffunction-sections -fdata-sections -momit-leaf-frame-pointer -fomit-frame-pointer -march=i486 -mtune=i486 " LDFLAGS=" -Wl,-Os,--gc-sections,-s "./configure --build=i486-t2-linux-gnu --prefix=/usr --sysconfdir=/etc --localstatedir=/var  $CONFOPTS

If you notice, there is no space between LDFLAGS=" -Wl,-Os,--gc-sections,-s " and ./configure --build=i486-t2-linux-gnu --prefix=/usr --sysconfdir=/etc --localstatedir=/var $CONFOPTS -- I inserted a space and that configure command ran after displaying the configure help in gtkdialog - thus guaranteeing that it actually configged with the options I chose.

Should probably be fixed if that is in error.
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4351

PostPosted: Mon 24 Aug 2009, 18:56    Post subject:  

good catch, I'll make sure to fix that in the meantime the file is /usr/bin/src2all

use this code to automagically patch it

Code:
sed -i 's/.\/configure/ .\/configure/' /usr/bin/src2all

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Wed 26 Aug 2009, 01:51    Post subject:  

Yeah. My only problem now is I tried to build Transmission (newest 1.74) and got everything BUT the program, using pcompile. LOL.

Something odd, I'll figure it out I guess, but still. It works at least. Smile
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Sat 10 Oct 2009, 23:03    Post subject: My changes, submitting a modified pet...  

Thought I'd revisit this little topic, and take another look at src2all and its buddies.

I made a few changes I thought you'd like, technosaurus.

First, fixed the bug we found earlier, with the space before ./configure
Second, put the "default" extras straight into the already-included options, changed the text to reflect.
Cleaned up the pcompile interface window with that in mind a bit.

Tried to make the labels look a bit better and not be over-spaced, but no dice - text formatting in gtkdialog is spotty with that kind of wording.

Wanted to add in a button that would trigger the ./configure --help but no dice there either, too complicated to pull off.

Well anyhow, have a look see if it plays nice for you. I used these changes to compile and build SDL and various SDL-Subgroup PETs, with plenty of success.
pcompile-0.1.1.pet
Description  PCompile 0.1.0 with changes made, 0.1.1 resulting version suggested. This is an unofficial pcompile version.
pet

 Download 
Filename  pcompile-0.1.1.pet 
Filesize  4.11 KB 
Downloaded  539 Time(s) 
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4351

PostPosted: Sun 11 Oct 2009, 00:11    Post subject:  

Maybe some checkboxes that default to TRUE that way they can be unchecked for packages that fail if that option is not available... then put them together in one string to pass to src2all (maybe src2all can just be part of pcompile now)
_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Sun 11 Oct 2009, 01:33    Post subject:  

Spoke too soon, found another glitch I never found before -- out of sheer luck apparently.

When handling bzip/bz2, src2all passes the arg -xyf to tar. Sadly, the tar version in Puppies 431 (and probably puppy 4.3.0 / upcoming 4.3.1) doesn't like y, and fails out. tar -xf <arg> seems to work, so modified it too.

I'll reply to your other suggestion in a moment.

*sigh*. Now to rebuild the damn pet and repost.
pcompile-0.1.1.pet
Description  use this one, not the previous one. Fixed tar bug in src2all
pet

 Download 
Filename  pcompile-0.1.1.pet 
Filesize  4.1 KB 
Downloaded  522 Time(s) 
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Sun 11 Oct 2009, 01:45    Post subject:  

technosaurus wrote:
Maybe some checkboxes that default to TRUE that way they can be unchecked for packages that fail if that option is not available... then put them together in one string to pass to src2all (maybe src2all can just be part of pcompile now)


To be honest that sounds really spectacular. Have it trigger a default options dialog with those checkbox to turn them off if need be, and instead of having default settings in src2all just have them passed in the config file that's passed.

While joining them together may theoretically speed things up a little bit, I don't think the time is that big of an issue. Compared to the fact that src2all is already rather... disconcertingly complicated...

But I love the checkbox idea.

Pity my skills with gtkdialog have already proven... lacking.

That being said, some of the options are almost guaranteed to be there, like prefix, and build. So those can remain.
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Sun 11 Oct 2009, 14:02    Post subject:  

Another thought.

Some packages (like GlibC which I'm trying desparately to compile the newest version for puppy - a game requires 2.7, and all the depos have 2.6, and I can't compile 2.10 due to some falloc call being undefined) require building from a separate build directory.

I tried building and doing 2dirs and dir2pet from a separate directory, called pcompile_build, located inside several different package dirs.
doing all the commands, building, doing 2dirs, and then doing dir2pet on the proper location, all worked from inside that build directory.

In the interests of keeping everything clean and orderly in the main package directory, pcompile should probably do that, I think.
I can rewrite some lines here and there to make it work, and post that later today.
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Sun 11 Oct 2009, 15:02    Post subject:  

Alright, can't compile GlibC as it'll put puppy in a bag and drown it in the river:( ... but I put in the changes to make it do what I mentioned above, and it seems complacent...

One question, though, there's the python setup.py command in there, does setup.py get created by ../configure or is it usually in the main src directory anyhow? I'm not sure whether to drop back to the main directory to run that setup.py or not...
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Sun 11 Oct 2009, 15:05    Post subject:  

Also, and this is just my personal thing with it, since /root/my-applications is in the Path and LD Lib path, my changes put the files into that location, specifically /root/my-applications/bin -- This way I can find them easier for those on-the-fly changes and tests... <G> this is just for the pcompile files, not the files compiled - those still sit in /usr since there's no corresponding directories for etc, share, and the like.

As far as the checkboxes, I can put them in but damned if I understand how parsing works in Linux, so I'll leave that up to you techno. Smile

But I'll have them in there, and comments, and lots of documentation on what I can document for the script, so it's understandable kinda...

God, nobody tell my programming professor I've been *gasp* documenting code, it'll give him a conniption.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 12 [172 Posts]   Goto page: Previous 1, 2, 3, 4, ..., 10, 11, 12 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Unsorted
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1008s ][ Queries: 13 (0.0207s) ][ GZIP on ]