Re: [cmake-developers] Feature suggestion: auto-create missing files

2017-04-13 Thread Petr Kmoch
OK, I can see there's quite a few voices against and none for. Idea scratched. Thanks everyone for input. Petr -- 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

Re: [cmake-developers] Feature suggestion: auto-create missing files

2017-04-12 Thread Ben Boeckel
On Tue, Apr 11, 2017 at 21:28:40 +0200, Alexander Neundorf wrote: > personally I'm not convinced. > Technically it would violate the "the source dir is read-only" rule. > A typo would generate files. With multiple build dirs the behaviour will be > slightly different in the two dirs. > ...not

Re: [cmake-developers] Feature suggestion: auto-create missing files

2017-04-11 Thread Alexander Neundorf
On 2017 M04 11, Tue 11:52:52 CEST Brad King wrote: > On 04/11/2017 11:41 AM, Petr Kmoch wrote: > > Currently, adding a new source file to a CMake-controlled project > > means doing two things: creating the file on disk, and adding it > > to the relevant CMakeList add_library() or add_executable()

Re: [cmake-developers] Feature suggestion: auto-create missing files

2017-04-11 Thread Ben Boeckel
On Tue, Apr 11, 2017 at 11:52:52 -0400, Brad King wrote: > If this were to be done I'd first like to see a policy introduced to > get rid of the magic extension guessing we do now. Without knowing > the full file name with confidence we wouldn't be able to create it. This is already an issue

Re: [cmake-developers] Feature suggestion: auto-create missing files

2017-04-11 Thread Petr Kmoch
Thanks for the quick response, Brad. On 11 April 2017 at 17:52, Brad King wrote: > On 04/11/2017 11:41 AM, Petr Kmoch wrote: > > Currently, adding a new source file to a CMake-controlled project > > means doing two things: creating the file on disk, and adding it > > to

Re: [cmake-developers] Feature suggestion: auto-create missing files

2017-04-11 Thread Brad King
On 04/11/2017 11:41 AM, Petr Kmoch wrote: > Currently, adding a new source file to a CMake-controlled project > means doing two things: creating the file on disk, and adding it > to the relevant CMakeList add_library() or add_executable() call. I view this as a matching pair with an implicit