User forums > Using Code::Blocks

cbp2make - makefile generation tool

<< < (15/25) > >>

oswjk:

--- Quote from: mirai on November 24, 2011, 05:37:38 pm ---
--- Quote from: oswjk on November 24, 2011, 10:46:12 am ---There's something fishy going on with global variables.
I've got these in the global configuration:

--- End quote ---
Yeah, I see. There's something wrong with target and macro variable casing.
While one of identifier casings (upper,lower,as-is) follows the configuration, another one does not.

Thanks for your effort. This is definitely a bug and I will fix it ASAP.

p.s. Please, send your project file (.cbp) to mirai.computing@gmail.com so I could test against it. I don't have any active projects with global variables in setup.

--- End quote ---

I'll send you one tomorrow when I'm back at work.

mirai:
Update: (see rev.125)

[+] Implemented toolchain selection without explicit duplicates.
[+] Added an option to control case of macro variables. Use "--macros-case [lower|upper|keep]" option to select casing for macros. Defaults are also changed, macros now are all in upper case while targets are all in lower case by default.
[+] Fixed case mismatch issues for global compiler variables.
[+] Fixed platform selection. It seems that for many revisions along selecting a single platform/OS would bring all incompatible targets to makefile, however, selecting multiple platforms never lead this bug.

mirai:
Update: (see rev.127) a quick bugfix release

[+] Fixed possible crash due to undefined toolchain introduced somewhere between rev.120-125.
[+] Revisited global compiler variable evaluation code. Some strings previously have escaped macro substitution, now that is corrected.

mirai:
Update: (see rev.130)

[+] Implemented handling of spaces and special characters in paths.

Try this revision if you previously experienced any problems with 'make' complaining about wrong paths.

Alpha:
From my personal experience, this is a useful tool which does exactly what it is supposed to do in the vast majority of cases.  I would suggest it be considered for inclusion in Code::Blocks' svn (in trunk/src/tools).  What do other people think?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version