you should always use cmake to build out-of-source. or something like
a 'build' directory in the source...
On Mon, Jul 9, 2012 at 9:32 AM, Romain LEGUAY wrote:
> Thanks for your answer!
>
> But I think if I do a 'cmake .' in lib dir or a application folder, I am
> going to have some problem no?
Thanks for your answer!
But I think if I do a 'cmake .' in lib dir or a application folder, I am
going to have some problem no?
Romain
Le 09/07/12 18:14, J Decker a écrit :
${CMAKE_SOURCE_DIR} this is the directory of the root CMakeLists.txt
that is processing, you can base your other paths
${CMAKE_SOURCE_DIR} this is the directory of the root CMakeLists.txt
that is processing, you can base your other paths off of that.
On Mon, Jul 9, 2012 at 6:58 AM, Romain LEGUAY wrote:
> Hello everyone,
>
> I have a big project organized like this:
> root/
> -> CMakeLists.txt
> CM
Hello everyone,
I have a big project organized like this:
root/
-> CMakeLists.txt
CMake/
--> some .cmake scripts
lib/
--> CMakeLists.txt
include/
src/
CMake/
--> some .cmake scripts
apps/
On 2009-11-09 12:52-0800 Phil Smith wrote:
I'm working with a CMakeLists.txt file I didn't create, so this may be a dumb
question, but that won't stop me from asking it!
We're using a System z cross-compiler called Dignus. I have it all working, but
when we merged back into the SVN trunk, the
I'm working with a CMakeLists.txt file I didn't create, so this may be a dumb
question, but that won't stop me from asking it!
We're using a System z cross-compiler called Dignus. I have it all working, but
when we merged back into the SVN trunk, the PROJECT() statement became an issue.
CMake i
