On Wed, Dec 9, 2015 at 9:52 PM, Attila Krasznahorkay
<attila.krasznahor...@gmail.com> wrote:
> Probably not the intended solution, but what I’m doing in such cases is that
> in a patch step I create a shell script that does the configuration for me.
> With all the environment settings and everything. Like:
>
> PATCH_COMMAND ${CMAKE_COMMAND} -E echo “cd someDir/; CC=\”something\”
> ./configure” > configure.sh
> CONFIGURE_COMMAND sh configure.sh
Thanks Attila for the tip. In fact, since you are already constructing
the command as a string, why not just run it through sh?
CONFIGURE_COMMAND sh “cd someDir/; CC=\”something\” ./configure”
--
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
