I've actually used that workaround, but it seems dirty as it shows up in
IDE targets like Visual Studio or other IDEs or makefiles. In fact, I
kind of like the 'generating /docs' part of the makefile.
Would it just be smarter to rename the target to 'documentation'?
--
Powered by www.kitwa
I have the following code:
# -- DOXYGEN
find_package(Doxygen)
set(docsDir "${CMAKE_BINARY_DIR}/docs/")
add_custom_command(OUTPUT ${docsDir}
COMMAND ${CMAKE_COMMAND} "-E" "make_directory"
${docsDir} VERBATIM)
add_custom_target("docs"
COMMAND "${DOXYGEN_EXECUTABLE}"
"${CMAKE_SOU
Ah, thanks guys. STREQUAL does the trick. Sorry for the bother and lack
of quotes.
Jookia.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic
Running the follow file causes problems:
if(NOT "${CMAKE_BINARY_DIR}" MATCHES "${CMAKE_SOURCE_DIR}")
endif()
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please k
Greetings from the world of CMake problems,
I've been using CMake for a while (love it!) but a while back I sent my
project off to a person and he tried to generate the CMake project, but
it failed. Why? Because he for some reason keeps all his data in /s . So
when CMake had the path /s/progra
