This isn't a bug but more of a weird side effect of having your executable named the same as an include file and adding the destination directory for the executable in the include path. The same thing would happen if your executable was named foo and you had "#include <foo>". By setting CMAKE_INCLUDE_CURRENT_DIR to on then CMake is adding -I/path/to/source/blink and -I/path/to/build/blink to the compile line. The default destination for the list executable also happens to be /path/to/build/blink. The second time around, the list executable from the first run is in the include path, thus #include <list> picks up the executable instead of the C++ header.
--
Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
