Hi,
What is mentioned here has been implemented in our configuration system
(CMT previously implemented in pure C++/make and currently
re-implemented on top of CMake)
The principle is to add on top of the build system (say CMake, but this
could be plain make, or Waf) a layer that describes
Hi Eli,
On 21 June 2012 21:25, Ateljevich, Eli e...@water.ca.gov wrote:
Hi,
I was wondering if there is a best practice for providing a file for user
configuration decisions (options, unique flags) that will be more
persistent than the cache? I have a project where a dozen or two
.
Thanks again.
Eli
From: cmake-boun...@cmake.org [cmake-boun...@cmake.org] On Behalf Of Ben Morgan
[bmorgan.warw...@gmail.com]
Sent: Friday, June 22, 2012 8:32 AM
To: cmake@cmake.org
Subject: Re: [CMake] Text user configuration (features, flags) that is more
persistent
Hi,
I was wondering if there is a best practice for providing a file for user
configuration decisions (options, unique flags) that will be more persistent
than the cache? I have a project where a dozen or two algorithmic decisions
have to be made. I find that this is just enough that cache
