On Thu, May 15, 2014 at 23:52:18 -0700, Alan W. Irwin wrote: > Just in case I run into command-length limitations for the cmd > environment in other contexts that cannot be solved so neatly, I am > also wondering if cmd has a general mechanism (e.g., reading from a > file) to work around its severe command-length limitations. And if > so, could the COMMAND implementation be changed to use that mechanism > behind the scenes when the cmd environment is detected without > changing the add_custom_command or add_custom_target syntax in the > slightest?
Not everything supports response files (it's usually compilers and MS tools). One thing we could do is detect when an add_custom_command or add_custom_target might run foul of command line length limits and warn for it. I don't know what else we could do without teaching CMake about every command's semantics. I suppose we could add response file wrappers around all long command lines, but command line parsing on Windows can be 100% custom, so there might need problems there :/ . --Ben -- 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/cgi-bin/mailman/listinfo/cmake-developers
