Hmm, you're right, I just tested and it seems the INSTALL_DIR is ignored or not handled properly, I'm not sure why. But if you use the CMAKE_ARGS option to manually set "-DCMAKE_INSTALL_PREFIX=/tmp/Fusion/qhull-2015.2" it works, so at least there's an easy workaround. Maybe someone else knows how the INSTALL_DIR option is meant to be used?
On Mon, Aug 29, 2016 at 11:00 AM, Michael Jackson <mike.jack...@bluequartz.net> wrote: > So that was a typo on my part but changing it had no effect after deleting > every build/download/tmp/stamp directory and trying again. > > -- > Michael A. Jackson > BlueQuartz Software, LLC > [e]: mike.jack...@bluequartz.net > > > Nicholas Braden wrote: >> >> Have you tried changing the = to a space, as with the other parameters? >> >> On Mon, Aug 29, 2016 at 10:52 AM, Michael Jackson >> <mike.jack...@bluequartz.net> wrote: >>> >>> I have the following CMake file: >>> >>> set(QHull_GIT_REPO "git://github.com/qhull/qhull") >>> set(QHull_GIT_TAG "") >>> set(QHull_INSTALL_NAME "qhull") >>> set(QHull_INSTALL_NAME "qhull-2015.2") >>> >>> >>> ExternalProject_Add(${QHull_INSTALL_NAME} >>> PREFIX ${Fusion_SDK_ROOT} >>> URL "http://www.qhull.org/download/qhull-2015-src-7.2.0.tgz" >>> INSTALL_DIR=/tmp/Fusion/qhull-2015.2 >>> LOG_DOWNLOAD 1 >>> LOG_UPDATE 1 >>> LOG_CONFIGURE 1 >>> LOG_BUILD 1 >>> LOG_INSTALL 1 >>> >>> ) >>> >>> and when I invoke the initial cmake with this: >>> >>> cmake -G Ninja -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Release >>> -DFusion_SDK_ROOT=/tmp/Fusion_SDK ../ >>> >>> I get a valid "configure" step. Then I run "ninja" and I get errors on >>> installation. The errors are because CMake is attempting to install QHull >>> in >>> /usr/local/lib. >>> >>> Why is that? I am not sure what I am doing wrong as this seems like a >>> pretty >>> trivial case. I have cmake 3.5.1 and read the docs at >>> https://cmake.org/cmake/help/v3.5/module/ExternalProject.html but somehow >>> cmake is messing up. >>> >>> Thoughts? >>> >>> >>> -- >>> Michael A. Jackson >>> BlueQuartz Software, LLC >>> [e]: mike.jack...@bluequartz.net >>> -- >>> >>> 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 > > -- > > 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 -- 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