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 Fri 31 Oct 2014, 19:13
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 5 of 12 [172 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, ..., 10, 11, 12 Next
Author Message
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Tue 13 Oct 2009, 20:19    Post subject:  

technosaurus wrote:
Actually I only did a simple fix - use $1 $2 and $3 as before, but use them to set the default values, if you use it the same as src2all and all is good just click OK and you get the same behavior. I did have to set up a slightly different case for when there were no entries. The only difference is that there is a GUI there that will let you make some quick changes in a more readable interface before you let it go through the hours long process of compiling Wine-2.0 or whatever without NLS or some other useful feature because of a typo or something.


LOL I got the last part but for some reason my mind just jellied on the middle.

This was for dump2pet right? Listen if you want I could integrate src2all into pcompile - it's not hard and would serve some benefit as I said earlier. How's the other stuff feel/look?
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4353

PostPosted: Wed 14 Oct 2009, 10:21    Post subject:  

integrating src2all will allow things like equal signs and quotes to be passed more easily, since echo strips them out unless you use escape characters and -e (with a preceding \) as well as specifying the busybox echo... for whatever reason just echo -e didn't seem to work even though it is a link to busybox but...
Code:
busybox echo -e

does work


All I was saying was that you could still enter the values from the command line ... it would just pop up the dialog to confirm and allow you to modify any typos etc...

_________________
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 14 Oct 2009, 15:03    Post subject:  

Ohhhhhhhh! Well then have you done any? cause if not I'll just integrate it right now and post a new copy. I've been DYING to find that out!

And echo shouldn't strip out those... I'll check...
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Wed 14 Oct 2009, 15:19    Post subject:  

Hmmm, a whole new problem.

It appears that calling a separate file has introduced something unpleasant... the gtk-file and gtk-open dialogs aren't triggering.

I don't honestly know why, so I'm trying it with the dialog copied back in as a single-quoted string (rather than double so I don't have to escape-quote everything)...

EDIT:

Had to doublequote and escape-quote...
BUUUUT...

It's still not calling the gtk-file and gtk-open anymore...

This is very odd.
The original pcompile I still have installed in /usr/bin - with its "already included" line instead of checkboxes... works fine.

I wish I knew when the problem was started... huh... wait I know.

Nevermind, false alarm.
I forgot to change a variable name in there one location... duh.

Okay ignore that. I'm gonna get back to what I was doing, testing echo losing = signs.

Just tested with new version...
It was the sed = thing that was stripping the = signs. Echo isn't losing the = signs, it works fine with my version. But I do agree at this point that it won't hurt to integrate anymore, especially given the ease of variable passing.

Here, unless any changes are made to src2all, I'll post in a new version with src2all still present but pcompile having src2all integrated (for testing).
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Wed 14 Oct 2009, 18:55    Post subject:  

Some changes had to be made here and there.

Notably, with the integration of src2all, the orange stdout box disappeared.

So, I made the pcompile command merely a wrapper, that calls the real script, located in /usr/share/pcompile, as pcomp_script

The other commands (dump2pet and 2dirs) remain in /usr/bin alongside the newly shortened pcompile.

As well, in the actual script, I made a few changes in how it works to clean up code execution and reduce speed loss.

Instead of doing 7 (!) greps to find out what file it is, I did an extension trim and a case statement.
Inside, to ensure correct extensions, there is one grep per case for 3 out of the 4 possible results -- greatly reducing the number of greps that may result.

In addition, an invalid package type will output an error message and exit the program with an error code 1.

Only running into a small snag here...
Trying to put the results of ./configure --help into a variable (I'm trying to output the contents to a variable then to a file, so as to not re-read from the file, and output the contents to another file at another location) ...

Tried using eval CONF_OUTPUT="./configure --help" and getting nothing.

If I backtick it it tries to execute every line of the output of ./configure --help - which is even more than less than unhelpful. Wink

How could I do it?

EDIT:

Doing eval CONF_OUTPUT="./configure --help" gives "--help command not found"... doing it with backticks I get EOF errors looking for matching single quote (').

Nothing I find online seems to do what I want <G>
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Wed 14 Oct 2009, 22:09    Post subject:  

Got it to take the value into the var -- with just `./configure --help` -- backticked command anyhow.

However, if I echo the variable to stdout, it shows with newlines and all just fine, all pretty.

If I output it to the file the way I had been up until now, it comes out without the newlines - everything all stacked on one line.

The other parts of the variable do come out nice and readable though.

I'm off to go somewhere for the evening, but if anyone has ideas it would be awesome, because this is about what's got me clogged up at this point -- I think the rest of the file works fine.
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Thu 15 Oct 2009, 02:19    Post subject:  

After a lot of struggling, I solved my problems on my own. Turns out I was stingy with my double-quotes. Adding a few here and there made it work. Wink

So, here it is. My submission for pcompile 0.1.5.

That being said, I'd suggest the final actual release version be 0.2.0 -- as it is this is in .tar.gz format because there may be further changes you like techno, or I might think of some stupid thing later on.

Anyhow, hope you like it.

Have a play, it all works, at least as far as I could test. Smile

Things remaining: src2all is still there, though obsolete.
dump2pet probably needs changes as you'd said.

setting up the pet.specs may be needed but that may already be done by dir2pet, and may want to change that in dump2pet... but that's yours.
pcompile-0.1.5.tar.gz
Description  pcompile, new version and new data. Enjoy!
gz

 Download 
Filename  pcompile-0.1.5.tar.gz 
Filesize  9.69 KB 
Downloaded  299 Time(s) 
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4353

PostPosted: Thu 15 Oct 2009, 21:11    Post subject:  

You have made a lot of progress on this since I last looked. I am working on adding the CFLAGS, CXXFLAGS and LDFLAGS that can just be plugged in to your work. I am attaching a gzip of the window file.

For 1.0 ... we could add some more common options, move to /usr/local (vs shared) and add some dialog boxes (just action buttons) to explain when to use which flags (basically from pet packaging 101 and some stuff I haven't added yet)

For 2.0 ... support for cmake and python...possibly run ldd on all of the bin, sbin and lib directories and filter them through sort and uniq to help determine dependencies
window.gz
Description 
gz

 Download 
Filename  window.gz 
Filesize  1.17 KB 
Downloaded  295 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: Thu 15 Oct 2009, 21:41    Post subject:  

Only problem with /usr/local is that on Puppy default 4.21 (and I think 4.3) /usr/local is NOT in the LD lib search path by default... and that causes anything put in libs there to fail out.

It's been a bug for some time which I've mentioned on other threads, but nobody seems to notice, or the common response is "So add it in yours"...

Anyhow, I already put those C/CXX/LD Flags into the code as you mentioned earlier -- or are you meaning to put them into the window function as well?

Name any and all common options and we can stick them in just fine.

Dialog boxes to explain when to use each flag -- perhaps we use Tooltips? Smile

Cmake and Python: You're a madman, sir, you go too far!! Wink
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4353

PostPosted: Thu 15 Oct 2009, 22:24    Post subject:  

Sorry should have clarified,... just the pcompile directory
FLAGS.png
 Description   
 Filesize   73.59 KB
 Viewed   620 Time(s)

FLAGS.png


_________________
Web Programming - Pet Packaging 100 & 101

Last edited by technosaurus on Thu 15 Oct 2009, 23:12; edited 1 time in total
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Thu 15 Oct 2009, 22:25    Post subject:  

Unless you mean moving pcompile into /usr/local -- that'd be fine. D'oh. Wink
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Thu 15 Oct 2009, 22:31    Post subject:  

Alright I went over the window file.

While I like what you're thinking, it will require an additional (one or two or three) extraction loops to determine the flags in the pcomp_script -- and I understand now what you mean.

Move the /bin into /usr/local/bin and move the share/pcompile into /usr/local/pcompile -- would that be about right?
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4353

PostPosted: Thu 15 Oct 2009, 23:14    Post subject:  

no need to move the stuff in /usr/bin just the stuff in /usr/share

Its not necessary - it could be anywhere - its just where the majority of the puppy projects are and thus where people would expect to find it

_________________
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 15 Oct 2009, 23:24    Post subject:  

That's fine. I think I can just make up another few loops for the other flags...

As it is, I'm going to look into renaming a bunch of the flag tricks so they're more descriptive.

I think %'s are gonna be included to make sure there aren't any false positives.
Back to top
View user's profile Send private message 
Gedrean


Joined: 05 Jun 2009
Posts: 138

PostPosted: Thu 15 Oct 2009, 23:36    Post subject:  

BTW, is it really bad to have the pcompile wrapper script reference the pcomp_script in a relative link rather than absolute? (in otherwords, ../local instead of /usr/local?)

Anyhow it'll be that way in debug until this gets fixed up Smile
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 5 of 12 [172 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, ..., 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.1620s ][ Queries: 13 (0.0836s) ][ GZIP on ]