2011/6/3 Jean-Christophe Fillion-Robin jchris.filli...@kitware.com:
Just tested it on linux and the same remark applies.
Hi,
I cannot find the answer in the ML archive but I think I already
crossed that issue in the past
and I was answered that this was the expected legacy CMake behavior.
1)
On Fri, Jun 3, 2011 at 9:10 AM, Eric Noulard eric.noul...@gmail.com wrote:
2011/6/3 Jean-Christophe Fillion-Robin jchris.filli...@kitware.com:
Just tested it on linux and the same remark applies.
Hi,
I cannot find the answer in the ML archive but I think I already
crossed that issue in the
if(argIsFile)
{
// Source CMakeLists.txt file given. It was probably dropped
// onto the executable in a GUI. Default to an in-source build.
this-SetHomeOutputDirectory(listPath.c_str());
this-SetStartOutputDirectory(listPath.c_str());
}
I'm too
I've noticed an inconsistency in CMake's generation.. For example I go
through the following sequence:
cd \Project
mkdir Debug
cd Debug
Then I either:
cmake -G Visual Studio 9 2008 -DCMAKE_BUILD_TYPE=Debug
..\CMakeLists.txt
It will generate, and then place the project files in \Project.
Just tested it on linux and the same remark applies.
//-
Case1:
mkdir TestCase1 mkdir TestCase1/Debug echo PROJECT(foo)
TestCase1/CMakeLists.txt cd TestCase1/Debug cmake ../CMakeLists.txt
Output:
-- The C compiler identification is GNU
-- The CXX compiler
