User forums > Help

Project build options confusion

(1/3) > >>

iw2nhl:
Hi,
in the "Project build options" dialog, you have a tree (in the left pane) that shows your project name as the root and your targets as leafs.
Each target has it's own options and this is right.
The project (root) has it's own options too, why? Who uses them?

Thanks,
Alessandro

sethjackson:

--- Quote from: iw2nhl on July 18, 2006, 04:04:57 pm ---Hi,
in the "Project build options" dialog, you have a tree (in the left pane) that shows your project name as the root and your targets as leafs.
Each target has it's own options and this is right.
The project (root) has it's own options too, why? Who uses them?

Thanks,
Alessandro

--- End quote ---

Because you may want all targets to have a few similar options/link libs etc. Like -Wall for example. :)

I use this all the time. The CodeBlocks.cbp project uses it. I'm pretty sure others use this alot too. ;)

iw2nhl:
Ok, this is useful, but then the presentation is not clear: how I know if an option is gloabally active and not in the current target? Have I to remember all global settings in my brain?

Example:
GLOBAL enables -Wall
RELEASE disables -Wall
DEBUG enables -Wall

In RELEASE I read that -Wall is disabled, but in fact it is enabled because of the global setting.

I think there should be a GUI representation of the gloabl status: you could use grayed check boxes for example.

MortenMacFly:

--- Quote from: iw2nhl on July 18, 2006, 04:04:57 pm ---The project (root) has it's own options too, why? Who uses them?

--- End quote ---
I for example use them. I've setup the warning levels to show on the project level and enable optimisation on the relase target and enable to include debugging options on the debug target.
...but you are right: to see the result would be nice. Currently you can achive this by showing the full compiler command line that is issued if you enable this option (see my sig how to do this). Maybe this can be done in another way, too (I think you have the visual studio dialog in mind...right?)

iw2nhl:

--- Quote from: MortenMacFly on July 18, 2006, 04:48:44 pm ---
--- Quote from: iw2nhl on July 18, 2006, 04:04:57 pm ---The project (root) has it's own options too, why? Who uses them?

--- End quote ---
I for example use them.

--- End quote ---
Sorry, I didn't express my thought in the right way: I did not mean "what developer uses them", but "what part of C::B uses them"...


--- Quote from: MortenMacFly on July 18, 2006, 04:48:44 pm ---...but you are right: to see the result would be nice. Currently you can achive this by showing the full compiler command line that is issued if you enable this option (see my sig how to do this). Maybe this can be done in another way, too (I think you have the visual studio dialog in mind...right?)

--- End quote ---
Thanks for the full command line option, this is very useful!
(I still hadn't used the "Settings" menu ;-))
Yes, I'm thinking about the visual studio dialog. Not to copy always from others, but why reinvent the wheel every time? Moreover that way is more intuitive and less error-prone (at least I think so).
Anyway that is only an idea, if there are better ones, they are always welcome!

Navigation

[0] Message Index

[#] Next page