Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-29 Thread David Cole
Chad, What is the value of CMAKE_BUILD_TOOL? i.e. output of: message(STATUS CMAKE_BUILD_TOOL='${CMAKE_BUILD_TOOL}') Why are you using ${CMAKE_BUILD_TOOL} anyhow when the command lines you're giving will only work with 'make'? -- Powered by www.kitware.com Please keep messages on-topic

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-29 Thread Chad Balen
Hi David, My output is: CMAKE_BUILD_TOOL='/usr/bin/gmake' I was originally using cd path/to/build/directory make #For some reason it doesn't recognize the make command if I leave out the path to the build directory but if you saw in the previous posts, Norman suggested to use

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-28 Thread Williams, Norman K
Cc: CMake Users cmake@cmake.org Subject: Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script Hi Norman, I used your CMakeLists script and I tried adding VERBOSE=1 likeso: BUILD_COMMAND ${CMAKE_BUILD_TOOL} VERBOSE=1 But I still get

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-27 Thread Williams, Norman K
I took what you did it and cleaned it up a bit, but I ran into the same issue. Strangely, in trying to debug it I ran Œmake VERBOSE=1¹ and THAT command succeeded where Œmake¹ by itself had that problem with finding the target ¹s¹ I then tried setting CMAKE_VERBOSE_MAKEFILE to ON and same thing,

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-27 Thread Chad Balen
Hi Norman, I used your CMakeLists script and I tried adding VERBOSE=1 likeso: BUILD_COMMAND ${CMAKE_BUILD_TOOL} VERBOSE=1 But I still get the same error (I also tried adding VERBOSE to the end of the CONFIGURE_COMMAND and INSTALL_COMMAND but same thing). Maybe it's worth noting in terminal the