If this is indeed the case I think the behavior should be modified to
respect CMAKE_CURRENT_LIST_DIR. Because, the parent include() command
hasn't completed until the nested include() commands have completed,
and I think it's a huge limitation that nested include() commands are
still referencing th
Hi,
On Fri, Sep 6, 2013 at 12:26 AM, Robert Dailey wrote:
> I have an interesting structure for my code & build scripts:
>
> root/
> source/
> CMakeLists.txt
> build/
> CMakeLists.txt
> cmake/
> common.cmake
>
> My root CMakeLists.txt is actually in 'root/source/build", and
I am attaching a sample that reproduces the issue. I'm using CMake
version 2.8.11.2. To reproduce this, just run the 'generate.bat' batch
file from its current directory (WINDOWS ONLY). I have set it up to
generate for Visual Studio 2008, but you can edit the batch file to
change this.
Password to
I have an interesting structure for my code & build scripts:
root/
source/
CMakeLists.txt
build/
CMakeLists.txt
cmake/
common.cmake
My root CMakeLists.txt is actually in 'root/source/build", and my
common scripts are in "root/cmake".
>From my root CMakeLists.txt file, I do
