DV_CO_CODE="`echo "${CHOOSER2#=}" | grep DV\|CO\|`"
# DV_CO_CODE should have the list of all Config Options DV's
DV_CO_RESULT=""
for COUNTER in $DV_CO_CODE
do
NAME=${COUNTER%=*} # Get everything on the left side of the =.
VALUE=$COUNTER
pcomp_strip VALUE $NAME # Now we have the value.
if [ $VALUE == "true" ]; then
NAME=${NAME#DV\|CO\|} # Strip the DV/CO indicator
NAME=${NAME/\&/=} # Replace & with =
NAME=$NAME" " # Format to include trailing space
DV_CO_RESULT=$DV_CO_RESULT$NAME # Stick it together
fi
done

I've got some concerns, one of these CFLAGS has an =2 and the other just has a 2, I'm not sure if these flags are exactly as you want them or not. For now, whatever's in the label is EXACTLY how it's getting pushed to the configure command line, so if you go through there and notice some arguments are wrong, they need to be fixed up.

Second, Optimization and Architecture - those are part of CFLAGS?

Third, should -O4 and -Os in LDFLAGS be together?

Also, the commas aren't gonna be in the label, they will be in the string overall, but thanks for the reminder.

Given that, I'm assuming Arch and Opt go to CFLAGS, and coding for that for now.

I like the user-defined sections.

I'm going to try and separate LDFlags and CFlags -- I'm not against a fourth tab, and I think the flow and spacing will work better, as it is CFlags has those three sets of args that are two-column instead of one, and they don't line up well -- admittedly gtkdialog has HORRIBLE layout options, so I'm gonna see just what I can make work to make everything look nice.
--That should also make the window a bit smaller -- it was smaller before, and while bigger isn't terrible, if we're pushing for Lowest Common Denominator I'd want to assume we're working with maybe an 800x600 screen at worst, maybe even 640x480, and so smaller is better if possible.

I don't think it's going bad though.

Keep up with it here, we're getting to a finish line and a release I think for v2. At this point we should release a v2 before moving on to further changes and alterations -- as it is the script code is nice and lean, I've stripped out a lot of things that aren't necessary... commented still but tried to get nicer.

So get back to me on those flags questions, and we'll see what we can pump out.

they are correct:
mpreferred-stack-boundary is looking for a power of two - in this case 2^2

the other fbranch... tells gcc to optimize branches toward the end after a bunch of other optimizations have been done

,-O4,-Os is a really hacky way of ensuring that the code size doesn't accidentally get increased... when linking gcc is supposed to look for -O, but there are plans to add the option of a numerical value (like -O[0-9]) so using -O4 prevents accidental generation of large and often broken -O3 bytecode and the subsequent -Os is there for the same reason. With Puppy's current gcc ,-O4,-Os is no different than using ,-O

btw gcc 4.4.2 is out now. I may build that later today while I am on a long car trip to go hiking with the family. It would be good to test the options on older and newer versions. I also have gcc 3.4.6 statically compiled against dietlibc to see how backward compatible it is._________________Check out my github repositories. I may eventually get around to updating my blogspot.

btw gcc 4.4.2 is out now. I may build that later today while I am on a long car trip to go hiking with the family. It would be good to test the options on older and newer versions. I also have gcc 3.4.6 statically compiled against dietlibc to see how backward compatible it is.

Maybe something good to suggest BarryK update in the next devx revision.

Barry is now working directly on woof & I am coordinating 4.4 CE, so it will definitely be in that. The biggest reason I started working on this was to make it easier for package maintainers, including myself, to update packages. We don't have a whole lot of "package maintainers" so another goal was to make it easy for beginners and intermediate users to contribute. I think we are getting there.

As for dump2pet / dmp2pet they could be part of the same script with the check builtin or separate scripts with the check in pcompile itself. The only thing I did not set up was a check for the specific distro for woof compatibility (to determine if it should be puppy, debian, slack ubuntu or arch) I just need to figure out where that info is... probably in a file in /etc_________________Check out my github repositories. I may eventually get around to updating my blogspot.

True, they can also be in the same script, as a whole function for each would work well to separate the code and make them easy to read.

If there are certain output functions that are needed, like gtkdialogs, it's possible to have it gtkdialog a single quote through a function... hmmm now I wanna see how THAT would work... Damn gotta keep off the side stuff.

should not need any dialogs. thats the whole reason I made dump2pet in the first place ... so that DEV DOC and NLS didn't waste so much time... the main pet will still call dir2pet which has its own dialogs.

I may update dir2pet as well so that all of the automatic stuff is done, a single dialog is brought up and then all the changes are made (again to avoid all the extraneous dialogs)

I also have dmp2pet writing the package database entry to ~/.pcompile.pets (I used the tilda for future multiuser compatibility) I would especially like to have the main package entered into that file as well

.... hmmm maybe I should have the defaulttextviewer open that instead. My whole reasoning behind this is that petspecs always puts the file in the same location with the same name and Nicoedit likes to forget the last entry when this happens, which would cause us to lose track of the db entry._________________Check out my github repositories. I may eventually get around to updating my blogspot.

So to have dir2pet do it all in dialogs instead of in the command prompt would be nice - since instead of doing that "type a character and hit enter" crap it's just got dialog box with entry boxes if needed, and maybe a separate tab for the ".desktop" entry... oooh I smell awesome... (in that this will be so awesome I can already smell it!)

And the package database entry stuff? Well... I have no clue about all that yet, so that'll be your area of expertise

Oh, and if you can, and it's convenient enough, could you give me, through all these CFLAGS in the first box there in your previously posted screenshot, a classification, like what they're for? Or maybe group them into two or more groups, in terms of what they're used for? I'm trying to figure out how I can nicely restructure out the CFLAGS list so it takes up less room wide and tall, and get all those CFLAGS groups together, then do the same for the LDFLAGS... it's mostly for layout purposes, I can try to make up something on my own if needed...

# Parse Dynamic Variables - Config Options
DV_CO_CODE="`echo "${CHOOSER2#=}" | grep DV\|CO\|`"
# DV_CO_CODE should have the list of all Config Options DV's
DV_CO_RESULT=""
for COUNTER in $DV_CO_CODE
do
NAME=${COUNTER%=*} # Get everything on the left side of the =.
VALUE=$COUNTER
pcomp_strip VALUE $NAME # Now we have the value.
if [ $VALUE == "true" ]; then
NAME=${NAME#DV\|CO\|} # Strip the DV/CO indicator
NAME=${NAME/\&/=} # Replace & with =
NAME=$NAME" " # Format to include trailing space
DV_CO_RESULT=$DV_CO_RESULT$NAME # Stick it together
fi
done
CFGOPTS=$DV_CO_RESULT$UCONFIG
# Now we have all the results, a final trailing space, and UCONFIG.
# This also works if either or both are empty.

# Parse Dynamic Variables - C/CXX Flags
DV_CF_CODE="`echo "${CHOOSER2#=}" | grep DV\|CF\|`"
# DV_CF_CODE should have the list of all CFlags DV's
DV_CF_RESULT=""
for COUNTER in $DV_CF_CODE
do
NAME=${COUNTER%=*} # Get everything on the left side of the =.
VALUE=$COUNTER
pcomp_strip VALUE $NAME # Now we have the value.
if [ $VALUE == "true" ]; then
NAME=${NAME#DV\|CF\|} # Strip the DV/CF indicator
NAME=${NAME/\&/=} # Replace & with =
NAME=$NAME" " # Format to include trailing space
DV_CF_RESULT=$DV_CF_RESULT$NAME # Stick it together
fi
done
# Leading and Trailing space in CFLAGS/CXXFLAGS string will be done when ...
# we build the string right before running ./configure
CFLAGS=$DV_CF_RESULT$UCFLAGS
# Now we have all the results, a final trailing space, and UCFLAGS.
# This also works if either or both are empty.

# Parse Dynamic Variables - LD Flags
DV_LD_CODE="`echo "${CHOOSER2#=}" | grep DV\|LD\|`"
# DV_LD_CODE should have the list of all LDFlags DV's
DV_LD_RESULT=""
for COUNTER in $DV_LD_CODE
do
NAME=${COUNTER%=*} # Get everything on the left side of the =.
VALUE=$COUNTER
pcomp_strip VALUE $NAME # Now we have the value.
if [ $VALUE == "true" ]; then
NAME=${NAME#DV\|LD\|} # Strip the DV/LD indicator
NAME=${NAME/\&/=} # Replace & with =
NAME=$NAME"," # Format to include trailing comma
DV_LD_RESULT=$DV_LD_RESULT$NAME # Stick it together
fi
done
# Leading and Trailing space in LDFLAGS string will be done when ...
# we build the string right before running ./configure
LDFLAGS=$DV_LD_RESULT$ULDFLAGS
# Now we have all the results, a final trailing comma, and UCFLAGS.
# If however UCFLAGS was empty, we do need to strip that trailing comma.
if [ $ULDFLAGS == "" ]; then
LDFLAGS=${LDFLAGS%,}
fi
# Now the LDFLAGS has either a properly formatted list, or nothing.

That's the loops code to extract everything from LDFLAGS, CFLAGS, and CONFIG OPTIONS...

Make sure if any vars are reused inappropriately, if you see something, say something!

EDIT: I forgot to put in the -Wl, so I can't continue till the question about -Wl that I raised in a few posts back:

By the way, what is -Wl in LDFLAGS? Is it always going to be included?

Is answered.

EDIT2: So I stuck -Wl hardcoded into the LDFLAGS code -- it seems happy.

I think that -Wl must be what tells gcc or whatever that the LDFLAGS are LDFLAGS...

Anyhow, let us be happy that it works, work on a bit of cleanup of the interface (it just feels so bad)...

All I need now is that categorization of the CFLAGS, any other categories they fit into would be great to separate them out if possible. If not, I'll tool around with the window code for formatting concerns, trying to make it all look even...

But I think this is good for a 0.2.0 release.

Works for either one you want to build too, woof or upup or ppup or whatever...

The defaults are to decrease code size, while the rest sometimes help make the program either start faster or run faster

LDFLAGS are not well documented
--gc-sections should be used with -ffunction-sections and -fdata-sections to "garbage collect" the unused ones (putting them in sections makes it easier for them to find) but using it on shared libraries can break things - so they should only be used for programs.

-no-keep-memory (not -fno-keep-memory) tries to save memory by having more disk read/writes where memory writes aren't necessary - this works well with the way Puppy is installed since Full installs are typicall of low ram machines and Frugal installs are typically loaded into RAM already so its not much of an issue there

--as-needed is one of those that I wish we could always use because it allows faster startup but some programs (Nicoedit for one) do not work with that flag... it doesn't load all of the shared libraries until they are needed

the `-relax' option performs global optimizations that become possible when the linker resolves addressing in the program, such as relaxing address modes and synthesizing new instructions in the output object file

-sort-common - Normally, when ld places the global common symbols in the appropriate output sections, it sorts them by size. First come all the one byte symbols, then all the two bytes, then all the four bytes, and then everything else. This is to prevent gaps between symbols due to alignment constraints. This option disables that sorting.

The gui dialog was a good idea too, the terminal dialog has been bugging me for a while since it is in a somewhat backgrounded terminal and can go unnoticed_________________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