Any reason that environment variables can't be used as cmake
variables? Like of course any cmake variable in a script would
override the environment, but if it's not otherwise found, checking in
the environemnt would make scripts prettier.
set BUILD_TYPE=debug
set BUILD_MONOLITHIC=1
cmake
2011/7/29 J Decker d3c...@gmail.com:
Any reason that environment variables can't be used as cmake
variables? Like of course any cmake variable in a script would
override the environment, but if it's not otherwise found, checking in
the environemnt would make scripts prettier.
set
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12371
==
Reported By:Michael Broutin
Assigned To:
On Thursday 07 July 2011, Alexander Neundorf wrote:
On Thursday 07 July 2011, Brad King wrote:
On 7/6/2011 4:00 PM, Alexander Neundorf wrote:
Since that Version.cmake file in most cases looks basically the same
They're only the same within a specific community's versioning scheme.
The
On 07/18/2011 03:43 PM, Alexander Neundorf wrote:
Done. There is now an enum which can have the values SCRIPT_MODE,
FIND_PACKAGE_MODE and NORMAL_MODE.
Good.
So, CMAKE_SIZEOF_VOID_P can be given to the script from the outside via -D.
Good. This should be encouraged. Is it feasible to
On Friday 29 July 2011, Brad King wrote:
On 07/18/2011 03:43 PM, Alexander Neundorf wrote:
...
Another question: the cmake.m4 is based on the m4-file for pkgconfig,
which has the GPL header at the top. So, the cmake.m4 still has that
header at the top.
Is this a problem ?
Yes. We at
On 07/29/2011 12:04 PM, Alexander Neundorf wrote:
On Thursday 07 July 2011, Alexander Neundorf wrote:
I think everything else are special cases, at least I can't think of other
generic cases.
How could another common scheme look like ?
Any ideas ?
Huh. I thought I responded to this one
