Hi these registry entries are added by cmake-gui and I don't see any
way for them to be cleared. Can you please create a new bug on
http://public.kitware.com/Bug/view_all_bug_page.php with this issue
and I will look into adding a feature to cmake-gui to clear dead
paths.
On Fri, Aug 15, 2014 at 12
OK, I partially take it back, you can set an environment variable that
references other environment variables even through the Windows UI...
But it's a little hard to grasp, because you see it when you're editing
the value, but then when you click OK, the view shows the resolved
value in the result
David-
> There are no "types" for environment variables.
Not in other operating systems, perhaps, but I think it's perfectly reasonable
to adopt the colloquial operating definition that, in Windows, the "type of an
environment variable" is the type of the Registry value used to hold that
envir
I have been using CMake to build a few open-source projects recently, and I've
been experimenting and moving around build directories and such. In a small
test application, CMake tries to find a library that I built and installed in
one place, and then I rebuilt and installed somewhere else. Mea
There are no "types" for environment variables.
There are types for values stored in the registry.
See this article: http://support.microsoft.com/kb/256986 and note the
descriptions of REG_SZ and REG_EXPAND_SZ.
The fact that you can do it in RapidEE does not mean it's a built-in
feature of W
Andrew-
You are correct that it was a Windows issue, not a CMake issue. See the post I
made about two hours before yours.
The problem isn’t the alphabetic ordering, though. Is the “type” of environment
variable. There are two types, “expandable string” and “string”. (There are
other types for
On 15.08.2014 01:59, matt.bol...@csiro.au wrote:
CDash will show a cut-down summary of where it thinks the errors or
warnings are but sometimes (especially with parallel builds) these are
wrong (or false positives) or alternatively everything succeeded but
you still want to browse through the b
> Apologies if this is a stupid question with an obvious answer staring
> me in the face but...
Nope, it's not.
The dashboard does not have the "full build log" because ctest does not
send the full output from the build step. Only the contents of
"Build.xml" are sent when a build is submitted to
hi all,
a combination of question and feature request:
i'm using a highly customized shell script to generate Info.plists on
osx. this build script has to make use of the usage requirements of the
corresponding target and it is called via a POST_BUILD custom command.
however this conflicts with
