The checkboxes were not well thought out - I don't know what I was thinking with that, but I came to the same conclusion when I started writing the bash for them.
No it's honestly a great idea, it just requires making this a little more standardized and less... simplistic.
To add a new category, we'd just need to add another loop with the right identifiers, and the right compilations, and use that in some command as a var instead of a fixed string.
The flags are still a good idea, we just want to properly format it out.
Also, we want to make sure that the top line in the window for that particular tab indicates these are advanced options, and should be left default if the user is unsure what they do.
Also add in rbuttons for mtune as well as march
also some programs keep their own FLAGS in the Makefile that override what you specify. Adding this line after ./configure will fix that
A specific (non-dynamic) checkbox in the app to check to request "override makefile flags" would be good for that concept.
To remove debugging support
Also, the removal of debugging support isn't REALLY necessary. A lot of changes I did so that program-breaking wouldn't occur, like the moving to a sub-dir instead of the main dir (when I was compiling some lib it was like "Not in the main dir, *****!")
Tell ya what, lay out the checkboxes the way you want, in the name just call them CB_<whatevername> for each option, make sure the frame indicates where they should go... and post here the format used for each section/flags/whatever --
(( meaning the format used in bash command line to make those flags active, so like cxxflags="blahblah" -- make sure it's clear how it's supposed to go with multiple options )).
I'll write up the code tonight or tomorrow. It's not at ALL hard to write up anymore. I've gotten the coding bug back and it's just a matter of figuring out how to work it.
BTW, are there any other characters we could do besides pipe and ampersand? Not saying I don't like those but I think & is only bad if it's at the end of a line - I'm not sure if filenames and stuff can have an & in it, so is there any other "command-breaking" characters?
If there aren't and those work fine I'll just use those.
It's no big deal, I just wanna make sure what I can and cannot do with this.