Does anyone know about this?
I've got a C++ project on Linux. I've been using CMake with it for a
while now.
In the past I had one directory per library or application that's in
my project. The other day I modified my project so that some lib/app
code directories are at directory level n, and
Christian Convey wrote:
Does anyone know about this?
I've got a C++ project on Linux. I've been using CMake with it for a
while now.
In the past I had one directory per library or application that's in
my project. The other day I modified my project so that some lib/app
code directories are
On 10/24/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Christian Convey wrote:
...
Can you create a test case that shows this problem?
I'm trying to, but it's very slow going because of the complexity of
the project. But I have noticed one thing. Look at the linkage
statement:
Linking CXX
The . probably comes from using CMAKE_CFG_INTDIR somewhere. It
evaluates to . in make file based builds, but it will be Debug or
Release for Visual Studio or Xcode based builds.
The CMAKE_CFG_INTDIR expands to something specific to the generator
used. For VS, it becomes $(OutDir) -- for Xcode, it
Hi Christian,
Have you considered using full paths, such as
${PROJECT_SOURCE_DIR}
and
${PROJECT_BINARY_DIR}
Juan
Christian Convey wrote:
OK, I've figured it out. Consider the following code. I use it to
decide, at cmake time, what subdirectories will be built in the
project (trust me - I
