Thanks all -- that worked. The key:
regedit.exe --> HKLM\SYSTEM\ControlSet001\Control\Environment\Path
had a backup of the path var before the CMake install nuked it.
> How long was your PATH before?
Just my luck, it was 1028 chars long (just 4 over the threshold).
> The installer is prod
> For every new release binary we run the installer by hand
> to verify that the interaction works. This doesn't happen to us.
Do you run it on a machine with PATH set to a string >1024 chars long?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http:/
On 04-Dec-15 03:47, Alexander Neundorf wrote:
On Thursday, December 03, 2015 09:27:29 Ruslan Baratov via CMake wrote:
> On 03-Dec-15 04:34, Alexander Neundorf wrote:
> > On Wednesday, December 02, 2015 12:27:42 Ruslan Baratov wrote:
> > If RPATH was _designed_ to be patchable, tools could jus
On Thursday, December 03, 2015 09:27:29 Ruslan Baratov via CMake
wrote:
> On 03-Dec-15 04:34, Alexander Neundorf wrote:
> > On Wednesday, December 02, 2015 12:27:42 Ruslan Baratov wrote:
> > If RPATH was _designed_ to be patchable, tools could just do it,
> > instead of having to implement worka
about recovering the path see
http://superuser.com/questions/523688/deleted-path-environment-variable-how-to-restore
On Thursday, December 3, 2015, Brad King wrote:
> On 12/03/2015 11:04 AM, Vasily Vladimirovich Vylkov wrote:
> > Installing CMake on Windows (7, 64-bit) with the "add cmake to sys
On 12/03/2015 11:04 AM, Vasily Vladimirovich Vylkov wrote:
> Installing CMake on Windows (7, 64-bit) with the "add cmake to system
> PATH for all users" option overwrote the contents of my PATH variable,
> instead of appending to it. This is horrible! I don't know of any
> way to recover my previ
Installing CMake on Windows (7, 64-bit) with the "add cmake to system
PATH for all users" option overwrote the contents of my PATH variable,
instead of appending to it. This is horrible! I don't know of any
way to recover my previous PATH value.
It also looks like this has been an issue in sever
On 12/2/2015 10:39 PM, iosif neitzke wrote:
Ah, okay, thanks. From cmake-gui the solution equivalent would be
selecting the Ninja generator but specifying native compilers (cl.exe
for this example) instead of using the default native compilers?
.
Yes, that would work as well. As long as cmake-g
For any arbitrary configuration in a multi-generator, I need to
determine if it's configuration is optimized or not (release or
debug). At the moment I thought I could do this by comparing against
the list of DEBUG_CONFIGURATIONS, however this property is empty if I
have not set it. I was expecting
Hi Nils,
Clever. I didn't even consider specifying the SOURCES argument of the custom
target with a generator expression. But it seems to work perfectly.
Thanks!
Attila
> On 03 Dec 2015, at 16:00, Nils Gladitz wrote:
>
> On 12/03/2015 03:47 PM, Attila Krasznahorkay wrote:
>> Dear
On 12/03/2015 03:47 PM, Attila Krasznahorkay wrote:
Dear All,
Is it possible to add additional source files to an already existing custom
target?
My project needs to generate a number of "different things", which it does by
setting up many custom commands. In order to trigger the generation o
Dear All,
Is it possible to add additional source files to an already existing custom
target?
My project needs to generate a number of "different things", which it does by
setting up many custom commands. In order to trigger the generation of
everything, I currently need to set up an inconveni
On 03-Dec-15 16:59, Johannes Zarl-Zierl wrote:
I.e. it could be replaced with a string of the same length or a
shorter one, but not a longer one.
CMake works around this by extending the build RPATH artificially with
":" at the end I think, patchelf works around this by making the whole
executab
> > I.e. it could be replaced with a string of the same length or a
> > shorter one, but not a longer one.
> >
> > CMake works around this by extending the build RPATH artificially with
> > ":" at the end I think, patchelf works around this by making the whole
> > executable one page bigger if th
I mean the latter, changing the build type in ide
On Thu, Dec 3, 2015 at 1:15 PM, Attila Krasznahorkay <
attila.krasznahor...@gmail.com> wrote:
> Hi Lloyd,
>
> You mean like:
>
> if( ${CMAKE_BUILD_TYPE} STREQUAL "Release" )
>set_target_properties( myexec PROPERTIES WIN32_EXECUTABLE TRUE )
> e
15 matches
Mail list logo
