16:05, 24 April 2017 г., Brad King <brad.k...@kitware.com>:
On 04/23/2017 01:30 AM, Konstantin Podsvirov wrote:
Where execute_process INPUT_CONTENT or INPUT_VARIABLE?
This would be very convenient for a small input.
Why should I always write a file for input?
I agree that the options should be there but they can't be easily
implemented without choosing our own temporary file which will have
its own problems.
The reason is that our internal process execution implementation
does not support communication from the parent on stdin. Fixing
that is not something I'm prepared to do or even accept as a
contribution because I'd rather migrate to libuv than extend our
own process management implementation further. That is a more
long-term process so in the meantime I think it is best to just
ask projects to use INPUT_FILE.
-Brad
I apologize. I saw the library libuv in the dependencies and thought that it was used in the current implementation.
I incorrectly assumed that this function is easy to add.
__
Regards
Konstantin Podsvirov
-- 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-developers
