Alright, new question. Are underscores "_" (not dashes "-") ever used in ./configure options, that we know of?

EDIT: Better yet. What characters are not able to be used in a bash command line string, for example as arguments of ./configure. That is to say, they must be \-escaped first, or just will not work b/c bash will interpret them as something else and screw up the command?

Wow, okay. I'm sorry to say that with decent documentation (documenting out in detail how I got my tricks to work, for example) the file size is HUGEMONGOUS for pcompile.

That being said, in pet form it'll be much smaller, but I expect overall the project may grow to single-digit kilobyte size.

At least, my submission for it.

HOWEVER -- I'm building it so that if we add another checkbox later for default options, then no additional code will need to be added to pcompile - thus the only changes need be done to the window file...
Oh, did I mention, I split off the dialogbox description into a separate file, so it's easier to read and manage?

If you want me to stop mutilating your project, techno, please say so. I hate to trod on toes.

I wouldn't really worry about size/speed too much. Speed should still be insignificant when compared to compile time and size will still be smaller than the smallest binary used during compilation. Keep in mind that it would require the devx anyway. Just wondering - have you gotten src2all to work with python programs?_________________Check out my github repositories. I may eventually get around to updating my blogspot.

I wouldn't really worry about size/speed too much. Speed should still be insignificant when compared to compile time and size will still be smaller than the smallest binary used during compilation. Keep in mind that it would require the devx anyway. Just wondering - have you gotten src2all to work with python programs?

I got nothing on that front.

As it is, I've got a while do done loop doing the checkboxes... With a little work... I finished the loop.

Now I've just got to reiterate my previous question:

Are there any characters in Bash which are UNABLE to be used in arguments by default, like % or whatever, that are unlikely to be included in ./configure arguments?

Alright, only question now is how does one work with a radio button? I'm not sure what all the returns are like from it... anyhow, it's getting there, the window at least. I got them as checkboxes, but I want to replace one or two of the prefix options with radiobuttons, to choose which locations to put stuff in.

There SHOULD be an attrib called Group, which would link a radio button to other radio buttons, all grouped to one primary (the default) so that they all control eachother.

Because I want multiple groups of Rbtns in this.

I'm thinking of moving to Glade, but I don't know that I wanna do it...
I really don't wanna redo this whole damn thing considering how far I've gotten so far... btw, here, uploading the latest version 0.1.3 - but it's not properly working, some things are commented out for debugging and it will throw up on a few things...

Oh and that window file will go in /usr/share/pcompile and be referenced from there in actual release, but for now it's designed to be run from terminal and in directory, not as installed...

uploading it as a tgz for that reason... I'll be honest the options tab looks crappy right now but I'm trying to do formatting and cleanup - but as I do formatting and try to make it look pretty it ungroups some of the RB's!

For now though, all the files that are currently up-to-date (still may be in a state of debug/repair) are in root/my-applications/bin I think... the usr folder just has stuff in there for placeholding I think...

pcompile-0.1.3.tar.gz

Description

TGZ format, not for working install/release, though it'll run as a dialog I think...

So, I was dicking around in Glade, noticing that radio button options had a Group attribute like I had hoped. It groups multiple sub-radio buttons to one, meaning that one of them is the default and the "master" of that group, whereas the others are all "slave" or sub items of that group...

With that I grouped radio buttons that were out of order, found it neat.

I'll have to look at it when I get home tonight. I started in a different direction (merging src2all) also noted that I need to look at dump2pet to bring it up to 4.3 for database entries (I also want it to >> to a separate file that will keep all of the database entries, since Nicoedit hiccups with files of the same name -- which was not an issue with the old naming scheme, but now they all have pet.specs vs. a named one)_________________Check out my github repositories. I may eventually get around to updating my blogspot.

I'll have to look at it when I get home tonight. I started in a different direction (merging src2all) also noted that I need to look at dump2pet to bring it up to 4.3 for database entries (I also want it to >> to a separate file that will keep all of the database entries, since Nicoedit hiccups with files of the same name -- which was not an issue with the old naming scheme, but now they all have pet.specs vs. a named one)

Well now isn't that a pickle.

I'd really recommend against merging, but that's just my claim of wanting to make sure that any individual file remains its own set of functionality, but that's just my programmer's instinct kicking in. Plus, with how complicated pcompile may become trying to build such a defined interface, it may grow very large -- and very large single file scripts do take more memory, I thought, unless it's something else about large single-file scripts that was a problem... I could be nuts there.

Oh well, anyhow, hope you have fun playing with the version I compiled so far. If you really want to merge src2all, it does keep the added benefit of not making a temp output file for the config options, though definitely one should be made in the base directory -- ALSO: I'd like to request that we output confopts to the base directory instead of tmp, since that gives a good reading later when custom configures can be made... maybe making it confopts.txt , I dunno if that's only a windows thing but I believe the use of the . extension makes it a bit easier to determine if a file should be something the user should read, or if it's just some data file that won't make much sense to the avg user...

I don't like the formatting I've got so far on the options tab, but I can't figure out how to make sure those buttons are linked together. I may just end up ditching the my-applications radio button idea and stick to some default compile options as checkboxes. Maybe do a little work to make them fit together clean.

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._________________Check out my github repositories. I may eventually get around to updating my blogspot.

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