I think you should be ok... just make another user admin before you do
it, of course. You can always put the user back by brute force, too, if
you discover you need it for something. I'm not aware of anything
special about the user besides its "admin-ness".
Good luck, and let us know if you fi
I just installed CMake 3.0 and I'm trying out the new generator
expressions for the target_compile_definitions() command.
I am doing this:
target_compile_definitions( ${project_name}
PRIVATE ${general_defs}
PRIVATE "$<$:${debug_defs}>"
PRIVATE "$<$:${release_defs}>"
Yeah I was just worried that since CDash seems to be so fond of this user it
might react badly to their forced departure.
Matt
-Original Message-
From: David Cole [mailto:dlrd...@aol.com]
Sent: Wednesday, 13 August 2014 11:37 AM
To: Bolger, Matt (DP&S, Clayton); cmake@cmake.org
Subject
You can always brute force it and go in and remove that user from the
database table with MySQL or phpMyAdmin...
HTH,
David C.
--
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 suppo
Hi All,
Does anyone know how to remove the primary (first) Administrator of a CDash
instance? All the other users show up with a 'make normal user' and 'remove
user' button but not the original administrator who setup the instance.
Thanks
Matt
--
Powered by www.kitware.com
Please keep messag
I only define:
BOOST_ROOT=C:\local\boost_1_56_0
BOOST_LIBRARYDIR=C:\local\boost_1_56_0\lib64-msvc-12.0
and this works Ok.
This will not work:
BOOST_LIBRARYDIR=%BOOST_ROOT%\lib64-msvc-12.0
If you go to a command prompt and type "set" you will see that %BOOST_ROOT%
is not expanded.
So this is a Wi
Thanks, Bill. As it turns out, the problem appears to be a bug in Windows.
Through experimentation, I have determined a truth about environment variables
that I have yet to be able to find spelled out anywhere: If the type of an
environment variable does not *need* to be "Expandable String", the
On 8/12/2014 12:44 PM, Chris Volpe ARA/SED wrote:
That’s a good thought, but unfortunately it didn’t pan out. I tried both
styles, and I even tried explicitly mixing styles like this:
BOOST_LIBRARYDIR=C:/local/boost_1_55_0\lib64-msvc-12.0
Or this:
BOOST_LIBRARYDIR=C:\local\boost_1_55_0/lib64-m
As it turns out, something weirder is going on, and it's not cmake's fault, so
I won't look for a solution here, but I'll describe the problem in case
anyone's interested. *Windows* is not expanding those environment variables.
First, I hacked up the installed version of FindBoost.cmake to spit
Greetings,
I tried to move from 2.8 to 3.0.1 today and I'm experiencing an issue with RC
files. Looks like a simple problem but I would be baffled if I'm the first to
experience this so I expect I have some kind of configuration issue. Here is
the offending snippet in the rules.ninja file:
rul
That's a good thought, but unfortunately it didn't pan out. I tried both
styles, and I even tried explicitly mixing styles like this:
BOOST_LIBRARYDIR=C:/local/boost_1_55_0\lib64-msvc-12.0
Or this:
BOOST_LIBRARYDIR=C:\local\boost_1_55_0/lib64-msvc-12.0
And those worked fine.
From: lucas.pet..
Hi David,
Thanks very much for your reply! That was extremely helpful, and will let
several packages document a functional workflow for the future.
On Tue, Aug 12, 2014 at 5:38 AM, David Cole wrote:
> Unless it is overridden somewhere else along the way, the following is
> used to create the li
On 08/12/2014 03:48 AM, Marcel Loose wrote:
> That's probably in the CMake 3.0.x docs; CMake 2.8.12 doesn't mention
> LINK_PUBLIC and LINK_PRIVATE in the policy documentation. I only read
> the following in the docs on target_link_libraries
>
>The LINK_PUBLIC and LINK_PRIVATE modes can be
On 08/12/2014 03:59 AM, Marcel Loose wrote:
> Another problem I faced with policy CMP0022 is that I was unable to
> really silence it. Setting the policy to OLD doesn't really work (at
> least not in my case), maybe because the "cmake_policy()" command is
> scoped(?).
For CMP0022 and CMP0023 the p
Unless it is overridden somewhere else along the way, the following is
used to create the link command line for a C++ executable:
(found in Modules/CMakeCXXInformation.cmake)
if(NOT CMAKE_CXX_LINK_EXECUTABLE)
set(CMAKE_CXX_LINK_EXECUTABLE
"
-o ")
endif()
As you
From
http://www.cmake.org/cmake/help/v3.0/command/add_custom_command.html :
"If COMMAND specifies an executable target (created by ADD_EXECUTABLE)
it will automatically be replaced by the location of the executable
created at build time. Additionally a target-level dependency will be
added so that
On 11/08/14 18:47, Brad King wrote:
> On 08/09/2014 09:46 AM, Marcel Loose wrote:
>> CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and
>> immediately deprecated the LINK_INTERFACE_LIBRARIES keyword,
>> triggering policy warnings CMP0022 and CMP0023.
>>
>> What is the proper w
On 11/08/14 18:47, Brad King wrote:
> On 08/09/2014 09:46 AM, Marcel Loose wrote:
>> CMake 2.8.12 introduced the keywords PRIVATE, INTERFACE and PUBLIC, and
>> immediately deprecated the LINK_INTERFACE_LIBRARIES keyword,
>> triggering policy warnings CMP0022 and CMP0023.
>>
>> What is the proper w
18 matches
Mail list logo
