Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Support for CodeBlocks in CMake
alex.neundorf:
But there is also the MakeCommands section, where I can specify the commands. cmake can generate the correct gnu make/nmake/etc. commands there, so it shouldn't happen that a wrong make is called.
(you can e.g. use GNU make together with cl to get parallel builds with cl, which nmake can't do).
Maybe this is also used for the parsing of the output to detect warnings and errors ?
Biplab:
Yes you can specify the command. But if unspecified $make variable would be replaced by the make utility of the current compiler.
alex.neundorf:
Ok, I committed some changes to the codeblocks generator.
It doesn't hardcode gcc anymore, it puts the include dirs for every target in the project file, it supports the different target types of codeblocks.
One question:
-what is the correct way to put a make command with a path with spaces in the project file ?
The following doesn't work:
<Build command="/usr/bin/make -f /home/alex/cmake/build\ dir/build-cb/Source/Makefile cmake" />
Putting \"the path\" in the project file worked worse, then CB couldn't load the project.
And some issues which are more feature requests/bugs:
Related: when CB loaded the project, it said there were errors, I should check the log file. Where is the log file ? (would be nice if the dialog would tell me where the log file is).
Also for targets of type library the toolbar offers "run" and "build and run" actions.
"Abort" didn't cancel the build (svn from two days ago).
Alex
Biplab:
--- Quote from: alex.neundorf on August 29, 2007, 04:18:13 pm ---Ok, I committed some changes to the codeblocks generator.
It doesn't hardcode gcc anymore, it puts the include dirs for every target in the project file, it supports the different target types of codeblocks.
--- End quote ---
But a bug has been introduced. The compiler id for MinGW on Windows is gcc Not mingw. :)
--- Quote from: alex.neundorf on August 29, 2007, 04:18:13 pm ---One question:
-what is the correct way to put a make command with a path with spaces in the project file ?
The following doesn't work:
<Build command="/usr/bin/make -f /home/alex/cmake/build\ dir/build-cb/Source/Makefile cmake" />
Putting \"the path\" in the project file worked worse, then CB couldn't load the project.
--- End quote ---
You've found a bug. :)
--- Quote from: alex.neundorf on August 29, 2007, 04:18:13 pm ---And some issues which are more feature requests/bugs:
Related: when CB loaded the project, it said there were errors, I should check the log file. Where is the log file ? (would be nice if the dialog would tell me where the log file is).
--- End quote ---
There is a Tab named "Build Log". Please look into it for errors. I guess it complained that -
--- Quote ---"Project - Hello" uses an invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!]. Skipping...
Nothing to be done.
--- End quote ---
alex.neundorf:
In a previous posing Thomas said about mingw:
> gcc natively on Windows32, no MSYS or Cygwin or whatever involved. Funnily, it's simply called "gcc"
> on my system, but that might be a relict from long long long ago, since I'm still using the same config
> as years ago.
So mingw gcc is called "gcc". Is mingw used in any other case ?
I have my sources here in "~/src dir/blah" and build always in "~/build dir/blah", so I always get the space related errors. So there is currently no way to quote/escape this properly for CB ?
Alex
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version