User forums > Using Code::Blocks

cbp2make - makefile generation tool

<< < (13/25) > >>

mirai:

--- Quote from: pacrook on July 15, 2011, 09:45:34 pm ---Not sure if this is something that could easily be fixed?  You could look out for special cases starting with `pkg-config --libs?
--- End quote ---
Where do you put this line in CodeBlocks project configuration? Maybe it should be on linker tab in list of libraries, then it will automatically go to LIB macro. As an alternative solution you can modify the command template for linker and change order of arguments.

mirai:
Update: (see rev.109) a bugfix release

[+] Fixed wrong makefile placement when working with a .workspace file, rewrote workspace makefile generation to rule-based approach.
[+] Fixed C/C++ dependency search (files in project directory, i.e. in current working directory, were not included).
[+] Fixed wrong path processing involving empty paths (some paths might end up with "dir/" or "/dir" or "/" instead of "dir" or en empty string)
[+] Implemented translation of project dependencies within a workspace into workspace makefile.
[+] Changed platform configuration, added parameter for "make" tool filename.

If there's something wrong in a fresh makefile, check cbp2make configuration (global "~/.cbp2make/cbp2make.cfg" or local "cbp2make.cfg" in current directory) - wrong (old) default parameters may be stored there. You can simply erase the configuration file to rewrite it with updated default values.

mirai:
Update: (see rev.110) back from another bug hunt

[+] Fixed target names in virtual target dependencies. Recently virtual targets were somehow broken and a garbage might appear in a makefile instead of targets' names.
[+] Fixed verbosity setting leading to missing project info output. Dependency information for source files was collected and passed to makefile rules, but it disappeared from regular output in verbose mode.
[+] Modified rules for stored configuration. Previously, cbp2make silently copied its default settings to a configuration file without any questions or notifications to allow further modification of those settings. As the code changes from one revision to another, an old configuration might become incompatible with a new code and result in buggy behavior without a real bug, which lead to confusion. Now cbp2make will not save default settings to a configuration file unless the user explicitly specifies "--config <option>" option to modify some settings. Also, cbp2make will indicate which configuration file it uses (none for initial/default mode).
 

mirai:
Update: (see rev.112)

[+] Fixed issue with missing toolchain index for linkers in multi-toolchain projects: all "$(LD#)" were falsely written as "$(LD)" even if a project had more than one toolchain with LD0, LD1, etc. macros defined.

 

mirai:
Update: (see rev.118)

[+] Fixed [wrong] unit index building procedure that ignored project constraints and attached all units to all of project targets.
[*] Updated documentation for stabilized code. However, it is yet far from being complete.
 
 

Navigation

[0] Message Index

[#] Next page

[*] Previous page