Hi Alan! 23.04.2017, 10:01, "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>: > On 2017-04-23 08:30+0300 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? > > Hi Konstantin: > > I assume that last sentence refers to using the CMake FILE command > directly to write the required file at cmake time in the build tree > (as opposed to having to create an actual permanent file in the source > tree to be used directly or as a prototype for a configured file in > the build tree)? If so, I use that approach quite a bit in various > build systems I have helped to develop to help drastically reduce the > number of small CMake-related files in the source tree. And I far > prefer that approach to what you seem to be asking for above which is > some added syntax variation to EXECUTE_PROCESS to provide the same > ability that the FILE command currently has. > > Note, I had to make some assumptions when answering you, and my > apologies in advance if I have misinterpreted anything you said > above.
You have correctly understood and assumed. Thanks for your reply. But imagine that we need to perform a simple process and process its standard output. But this process unfortunately awaits user input to complete. > > Alan > __________________________ > Alan W. Irwin > > Astronomical research affiliation with Department of Physics and Astronomy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the FreeEOS equation-of-state > implementation for stellar interiors (freeeos.sf.net); the Time > Ephemerides project (timeephem.sf.net); PLplot scientific plotting > software package (plplot.sf.net); the libLASi project > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > and the Linux Brochure Project (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ My suggestion: Add support for the INPUT_CONTENT or INPUT_VARIABLE arguments in execute_process command. It seems to me that this will be a very useful improvement. Will anyone take up the implementation of this improvement? -- 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