User forums > Using Code::Blocks

cbp2make - makefile generation tool

<< < (11/25) > >>

mirai:

--- Quote from: killerbot on May 09, 2011, 09:37:44 pm ---I have a cbp project, with the following targets : Debug and Release
I would expect the same casing is used :

--- Code: ---Debug: before_Debug out_Debug after_Debug
--- End code ---
What do you think ?

--- End quote ---
Generally speaking, I have nothing serious to oppose this idea.
Current naming scheme for both macro variables and targets was designed with two things in mind:
1) remove characters unwanted in makefile;
2) bring up some style to make makefile look nice and readable;
and 3) [just came up with this now] when everything is in low case, you don't have to switch case when typing "make <something>" ;) [this is merely a joke]

How do you think, would a kind of "--keep-target-case" option be a solution?

killerbot:
sounds ok for me. I personally would have expected this the default behavior.
But then again, I can live with your suggestion ;-)

mirai:

--- Quote from: killerbot on May 09, 2011, 11:12:57 pm ---sounds ok for me. I personally would have expected this the default behavior.
But then again, I can live with your suggestion ;-)

--- End quote ---
Considering the default and a non-default behavior, I have another idea. I'm thinking of putting a thing like "<default_options>bla bla bla</default_options>" into cbp2make.cfg and adding "--def-options "bla bla bla"" option to command line configuration. This way if you want options "--wrap-objects --with-deps --keep-target-case" (for example) to be default options, you have to run cbp2make once with "--def-options "--wrap-objects --with-deps --keep-target-case"" option among others. Those additional options are intended to be immediately attached to other options after reading cbp2make.cfg configuration file, but before doing anything else.

killerbot:
this can work too, but a command line option is always nice, so no copying of config files is needed to wherever you need within to over systems.

Let me explain  : why I expected it to be default behavior. If I decide in my cbp project to call, the target "Debug", then that was my choice. Then I would prefer that no-one is changing it to lowercase, even when it creates new stuff derived from my cbp file.
Say my output directory is Debug, then that one is case preserving, but the name is not when it is translated into a makefile target. Seems a bit inconsistent.

But as said, I can live with your other solutions.

mirai:

--- Quote from: killerbot on May 10, 2011, 01:03:03 pm ---Let me explain  : why I expected it to be default behavior. ...
--- End quote ---
Good point, I agree.


--- Quote from: killerbot on May 10, 2011, 01:03:03 pm ---But as said, I can live with your other solutions.
--- End quote ---
I would prefer the default solution to fit user needs better, not just that people could live with my other solutions.

How about that: add an option "--target-case" or "--target-style" with valid values "keep", "lower"/"lowercase", "upper"/"uppercase" and the default value "keep"?
Same solution may be applied to macro variables too...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version