So the bugfix would be to use the -D parameters, given to cmake-gui, when configuring a completely new project (=> cache is empty/non existing)? That would make sense to me and shouldn't be hard to implement.
On Sat, Nov 2, 2013 at 1:00 PM, David Cole <dlrd...@aol.com> wrote: > -----Original Message----- >> From: J Decker <d3c...@gmail.com> >> To: physhh . <phy...@gmail.com> >> Cc: cmake <cmake@cmake.org> >> Sent: Fri, Nov 1, 2013 9:51 pm >> Subject: Re: [CMake] Forwarding parameters to cmake through cmake-gui >> >> >> sorry and I should ask; after reading a bit more context; >> >> why are you using cmake-gui if you have -D's to pass already? >> > > > It can make sense if you have a script that your users can run that > populate a handful of -D options automatically, but that still require > users to set some other options via the UI that are hard to determine > proper values for automatically. > > D > >
-- 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://www.cmake.org/mailman/listinfo/cmake
