Page 9 of 9

Posted: Sun 01 Nov 2009, 19:40
by technosaurus
I had planned to add a checkbox but In order to not break stuff I just had it make both - if you don't have xz and tar >1.21 you will only get a pet and an error - otherwise you will get both pet and pxt

the infobox is convenient for messages that you don't want to get in the way
Xdialog --infobox "Will automatically timeout in ($X/1000) seconds" 0 0 $X

Posted: Sun 01 Nov 2009, 22:44
by technosaurus
Need to figure out how to add an exit code to the configure options dialog that will let you easily restart pcompile if you hit cancel - any ideas? ... or should the configure options be separated?

for restarts maybe we should check for the confopts file and have a button to open them in the main gui

This is for the "Oh crap I forgot to enable/disable XXX" scenario.

Posted: Mon 02 Nov 2009, 00:56
by Gedrean
technosaurus wrote:gzipped tarballs - I may download the latest gzip and see if it supports leaving the existing file in place since some tar.gz files (specifically the ones for SDL and friends) are not recognized by tar for whatever reason (this is why I decided to add plain tar support in the first place)
That's really odd - I've not had it have ANY problems with the SDL packages - in fact those are the ones I end up compiling because they don't have any strange dependencies I don't already have.
I also changed some of the default values to false so that it doesn't stop a configure script due to a missing argument
Good thing.

Posted: Mon 02 Nov 2009, 00:58
by Gedrean
technosaurus wrote:I had planned to add a checkbox but In order to not break stuff I just had it make both - if you don't have xz and tar >1.21 you will only get a pet and an error - otherwise you will get both pet and pxt

the infobox is convenient for messages that you don't want to get in the way
Xdialog --infobox "Will automatically timeout in ($X/1000) seconds" 0 0 $X
The problem is, if I have it remain as dir2pxt, it just gives a /.pet message and NOTHING is made, so apparently your expected behavior is not what's happening.

Posted: Sun 08 Nov 2009, 00:07
by technosaurus
I will look into that tomorrow. I am planning to separate out the scripts again so that users have a chance to change configure options without rerunning the entire thing. I'm also adding a cleanup section to remove accidentally captured compile-time files. (for example <pkgdir>/root/my-documents/.... if you compile from there) ... needs to be done before copying the "extras". Will also revert back to tar -xf instead of using gunzip since it messes up the dirname portion - big 00ps.

Posted: Tue 14 Feb 2012, 13:32
by sunburnt
Hi technosaurus; Old thread, hope you still have interest in it.

As to configure options, saving all of them in a config. file would be good.
A config. profile file selector combo perhaps, the default config. at the top.

I`ve used the cli arguments to fill the source file and the user def. opt.
I need to set user def. opt.: --prefix=/tmp/apps.sq/mnt/( SrcFileName )
It conflicts with the checkbox: "--prefix=/usr" ( A saved config. would fix it.)

I need to compile apps. to run in the path setup by --prefix .
PCompile has lots of options, I understand some of them.
Some of the options might be useful for building apps. like this.

It seems to me PCompile is capable of building for other Linux distros.
I need to understand the options better. Are you willing to discuss this?
Perhaps by PM so your forum thread stays cleaner?

Posted: Tue 14 Feb 2012, 22:06
by harii4
It seems to me PCompile is capable of building for other Linux distros.
I need to understand the options better. Are you willing to discuss this?
Perhaps by PM so your forum thread stays cleaner?
Other forum users might find such info useful as well? :wink:
It might be over my head but just saying.....

Posted: Tue 14 Feb 2012, 22:59
by technosaurus
I guess I could revisit this a bit, maybe even add download support too. It needs smarter handling for cflags too (gc-sections sometimes breaks plugins and xml based UI.) and some tooltips explaining various nuances for each flag.

Posted: Wed 15 Feb 2012, 16:04
by sunburnt
Download support? What repository?
I looked at Slack but I didn`t see many packages, maybe I missed them.
I tried with Debian but it`s a mess to try to follow dependencies.
Tiny Core Linux`s dependency tree files were complete.

Posted: Thu 16 Feb 2012, 20:45
by sunburnt
A GtkDialog gui I made, lists package groups, then packages and it`s info.

Posted: Thu 16 Feb 2012, 22:39
by technosaurus
Sorry for being unclear. I meant having an editable field for the source tarball's url (an edit box or editable combobox, with default as saved location if any exist). I recently made a xdialog progress meter for wget that would work nice.

I need to make a list of requirements first, so I can at least stub out additional features.

Post subject

Posted: Sat 18 Feb 2012, 15:58
by oldyeller
Hi technosaurus,

I am new to this compiling stuff and need a hand held help. I downloaded your pet and don't' know how to use it, So if you are willing can you help me.

I have lupu 528-004 and what two compile two programs. 1 fluxbox 1.3.2 and xiphos. Will do all the work for this just need help to get started.

I was able to do fluxbox through the terminal, but xiphos is way above my head.

Thanks,

oldyeller