I think it's a little strange to have multiple project file to manage one project it multiple configurations, instead of having a single project file for one project, that manages multiple configurations directly, isn't codeblocks made for that ?<br>
<br><div class="gmail_quote">2010/7/25 Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thursday 22 July 2010, Carlos wrote:<br>
> Hello,<br>
><br>
> It seems the debug/release default configuration are only built for VStudio<br>
> suites.<br>
> Anyway I am trying to simulated such for the codeblocks IDE, this is how I<br>
> did my CMakeLists.txt :<br>
><br>
> project( myapp )<br>
><br>
> add_executable( Release WIN32 ${my_src_files} )<br>
> target_link_libraries( Release ${my_libs} )<br>
> set_target_properties( Release PROPERTIES OUTPUT_NAME myappname )<br>
><br>
> add_executable( Debug ${my_src_files} )<br>
> target_link_libraries( Debug ${my_libs_dbg} )<br>
> set_source_files_properties( Debug PROPERTIES COMPILE_DEFINITIONS .... etc<br>
> .... )<br>
> set_target_properties( Debug PROPERTIES OUTPUT_NAME myappname_dbg .... etc<br>
> .... )<br>
><br>
><br>
> Actually this works pretty fine but :<br>
><br>
> Is that the right way to simulate VS build configurations ?<br>
<br>
</div>Hmm, the Codeblocks generator is makefile-based.<br>
Each makefile-based buildtree builds only one configuration.<br>
If you want multiple configurations, create one buildtree for each<br>
configuration (each with its own C::B project file).<br>
<div class="im"><br>
> Is there any chance this conflicts with the VS generator ?<br>
><br>
> Other misc question :<br>
><br>
> What are the xxx/fast configurations in codeblocks ?<br>
<br>
</div>They are for building the respective target, but without checking whether the<br>
dependent targets are up-to-date (i.e. if you build A and A links against<br>
B, "A/fast" will only check what needs to be built for A, but not check all<br>
source files of B whether they have to be rebuild. This saves the time for<br>
checking the dependencies).<br>
<br>
Alex<br>
</blockquote></div><br>