For now, a wrapper script is definitely the way to do this. We need the ability to specify environment values generically in the "add_custom_command" command. Once we have that, adding support to ExternalProject will be trivial. Until we have that, a wrapper script work-around is valid now and will still be valid after we add that feature.
There are no concrete plans that I am aware of to do this work in the near future. But when it is done (eventually), you'll probably hear about it first here on this mailing list... Thanks, David C. 2011/10/17 Milutin Jovanović <[email protected]>: > > Thanks Luigi. I feared a workaround was necessary. I will go over your > suggestion and try to apply it. > > I'll second your suggestion for providing environment variables for > ExternalProjects. > > Miki. > > > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
