I am sure you will reply to some of my points, ...
Nope. I'm done for now. :-)
but I would like to say
in advance that I appreciate your different point of view even though
I might not always agree with it, and I am sure vice versa.
Same here. Our society desperately needs more reasoned
cmake -E echo
with no further arguments is already pretty darned close to cmake -E
do_nothing...
For the configuration-specific custom commands, keep your eye on
http://public.kitware.com/Bug/view.php?id=9974 and its related bugs.
Eventually, I expect it will be possible. Sooner, if you
138%
make -j4 all examples_noinst
I've seen this too but never noticed a pattern about when it happens.
Does it always happen when naming more than one target with make -j?
I thought you were not supposed to name more than one target with make
-j... (but I don't understand fully exactly
Well, there's this information about unknown error -10810:
http://www.thexlab.com/faqs/error-10810.html
Does your app launch a lot of sub-processes at startup?
Are you saying that you *can* run the app from the terminal window, but
that you cannot run the app by double-clicking or by using
Also, you may find extra hints about what's going wrong in the output
of the Console application. (Usually found in
/Applications/Utilities) -- see if there's anything in the
system.log in there, or poke around and see if it has a crash report
related to your app.
HTH,
David C.
--
Powered
Answered on stack overflow. Copied/pasted here for mailing list
archives:
The references that get_prerequisites returns are not absolute full
path references, and they are also not resolve-able to absolute
references via a simple get_filename_component call. (On Mac, they may
contain
You can set CMAKE_CONFIGURATION_TYPES to your own list of
configurations (including limiting it to a single configuration) as
long as you set it *before* the project command in your CMakeLists.txt
file. This technique works with the Visual Studio and Xcode generators.
See the following bug
There is an option (which should be on by default) in the
Miscellaneous section of the project settings, which is
called: Show coverage code.
Thanks, this solves the problem. The option wasn't checked.
The option should be *OFF* by default.
If the intent is not to show your code (because
In fact, it's not just a documentation typo.. It occurs three times
in cmake 'next' and 'master':
$ git grep COPY_ONLY
Help/manual/cmake-packages.7.rst:COPY_ONLY
Modules/Qt4Macros.cmake: configure_file(${infile}
${out_depends} COPY_ONLY)
Source/kwsys/CMakeLists.txt:
The problem as reported, is that you're trying to use add_custom_target
with a target named test -- but you can't do that with CMake because
test is a built-in well-known predefined target name.
Other so-called well-known target names include all install
package and package_source. And there
Unfortunately, I always have to resort to source code analysis to
figure this stuff out... NamedMeasurement is only mentioned in the file
Source/CTest/cmCTestTestHandler.cxx :
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/CTest/cmCTestTestHandler.cxx;hb=refs/heads/master
(search the
By the way, this should be better documented in the cmake / ctest
documentation.
And we should be allowed to add measurements like these in the log:
Log message - date - DartMeasurement ...0.1/DartMeasurement
I agree on both points. I would go even farther and say what you were
trying to do
To the best of my knowledge, CMake does not do anything with .targets
files. It doesn't know what they are, and it doesn't generate any of
them...
What is the function of the .targets files in your non-CMake build
system?
Perhaps somebody else who is more familiar with .targets files is
CMake itself does this to include a file at ctest time that applies to
*all* tests:
set_directory_properties(PROPERTIES
TEST_INCLUDE_FILE
${CMake_BINARY_DIR}/Tests/EnforceConfig.cmake)
It results in this line being generated in CTestTestfile.cmake at the
very top of the file:
So from the example you've sent, it seems like the stuff in your
targets file is just a bunch of custom commands that you'd need to run.
There are plenty of examples of projects using add_custom_command and
add_custom_target out there, and if you have specific questions about
how those
First try this:
-Original Message-
From: Ravi Raman ravi.ra...@xoriant.com
To: David Cole dlrd...@aol.com
Cc: cmake cmake@cmake.org
Sent: Fri, Aug 1, 2014 7:49 am
Subject: RE: [CMake] Cmake issue regarding conversion of existing
Visual Studio .targets files to cmake
Hi David,
We
Sorry about the premature send on that last email...
First try this:
add_custom_command(
TARGET ${TARGETNAME}
POST_BUILD
COMMAND ${TBIN}/VerCheck.exe \$(TargetPath)\
COMMAND copy \$(TargetPath)\
\$(TargetPath).vercheck_dummy_target\
COMMENT Checking
Ouch... my brain hurts...
Another idea would be to write the generated functions out to a file,
and then, after all functions are written to the file, include the file.
Might result in something you can actually look at in an editor (and
make sense of) without your brain hurting too much,
Seems like your best bet using CMake would be to use OBJECT libraries
for your Project01 through Project99 -- and then use STATIC libraries
for your ReleaseLibraries, which combine the objects of the appropriate
project libraries...
You may need to use dummy source files for the static libs,
What's in your toolchain file?
Is the file at C:/software/propgcc/bin/propeller-elf-gcc named
propeller-elf-gcc.exe? Should there be a .exe in the compiler file
name?
What GNU make are you using? (The primary ones well tested for use
with CMake on Windows are MinGW and MSYS...)
Can you
Specifically, for the OBJECT library feature, I figured out what
version of CMake introduced it like this:
gitk -- Tests/ObjectLibrary/CMakeLists.txt
leads to finding this first commit of that file: 69d3d183 [1]
gitk 69d3d183
leads to b87d7a60 [2] (4 parent commits up) which introduced
If it works, do it.
Custom commands are the easiest way to do MIDL stuff driven by CMake if
you need things to work with any generator.
Alternatively, if you are guaranteed to be using Visual Studio
generators, you can try just adding the idl file as a source file of
the library or executable
If silently installing is your objective, you may do so with an NSIS
built *.exe installer.
See this old blog post for details:
http://www.kitware.com/blog/home/post/186
HTH,
David C.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
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
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
CMAKE_CXX_COMPILER FLAGS
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
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
If x is a CMake-driven project, you'll also need to explicitly set
CMAKE_INSTALL_PREFIX when configuring. If not, there's likely a
--prefix arg for configuring... One of those also has to be set to
install to a non-default location.
The PREFIX arg for ExternalProject is only used to organize
See, for example:
https://github.com/OpenChemistry/openchemistry/blob/master/CMakeLists.txt#L24
A common CMAKE_INSTALL_PREFIX is used for all OpenChemistry
ExternalProject builds that are driven by CMake.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
--track is the same as the TRACK argument to the ctest_start scripting
command.
http://www.cmake.org/cmake/help/v3.0/command/ctest_start.html
It will send a dashboard to the named section of a CDash project page,
but it will NOT create it. You have to create the track (called a
group in
A SET(ENV{TARGET2_EXE_PATH} C:/Test/Target2) call in a CMakeLists
file only has an effect while CMake is running.
If you need the env var set for your batch file to run, you should pass
the value for it down in as an arg to the batch file, and then do:
set TARGET2_EXE_PATH=%~1
(no quotes
We have a fairly large project with about 400 targets.
$ cmake %builddir%
- takes about 5 minutes for a No-op
$ cmake --build %builddir% --target ZERO_CHECK
- takes 20 seconds for No-op
This is the problem.
cmake %builddir% should be as fast as possible for a no-op... If it's
not, it
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
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
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
Have you considered GetPrerequisites.cmake or BundleUtilities.cmake?
http://www.cmake.org/cmake/help/v3.0/module/GetPrerequisites.html
http://www.cmake.org/cmake/help/v3.0/module/BundleUtilities.html
It sounds like exactly what you're asking for.
HTH,
David C.
--
Powered by
Definitely getting warmer! It looks like that GetPrerequistes only
works on an existing target so I'm thinking I would have to set this
up as a super cmake project after the main project is already built?
Right, or as a script that runs at install time. It requires an
executable file to
Yes, the more I look at this the more I realize it's not going to
work. The script method is going to install the required libraries,
in my case on win32 no one is going to run make install it's
instead going to be make package.
But make package typically runs make install under the hood...
I thought using FindPythonInterp would be more portable than
simply invoking python directly (i.e. using $PYTHON_EXECUTABLE).
In case you want the newest version of any Python major, as in your
case, try
find_package(PythonInterp 2 REQUIRED). But you are right, this would
also successfully
Use ${CMAKE_CFG_INTDIR} in the context of add_custom_command OUTPUT,
not $CONFIG.
You may also use that in the COMMAND arguments.
See documentation here:
http://www.cmake.org/cmake/help/v3.0/variable/CMAKE_CFG_INTDIR.html
The $ generator expressions are relatively new, and do not work in
all
Ah, thanks... Though, I think there may be a general disconnect here:
that is, it seems likely that one would want to construct output with
a pattern composed from generator expressions.
...
While I gather from your comment that something like this might be
possible in the future, is there
First: thanks for your questions to the CMake list. However, when you
send an email to the list, please just ask the question -- that is,
please do *not* ask me by name. I know I've answered a few questions
for you in the last few weeks, but I am not the only one here, and
asking me by name
No need to add a bug for this... it's fixed already in 'master' -- that
means it will automatically appear in the next major release of CMake.
The current release is 3.0.1, and any critical bug fixes going into
CMake for a patch release will appear in 3.0.2, 3.0.3, and so on. (This
particular
Yes, but the warning text could certainly mention a missing closing
quote as a possible cause, and it could also avoid repeating itself
infinitely... The first occurence should be enough to pinpoint the
problem upon investigation.
Presumably, Dan, this was followed by an error of some sort as
Sometimes an unfortunate network interruption (even a very brief one,
at just the wrong time...) can cause my bullseye dashboards to report
0% coverage. I use the license manager for Bullseye, so the build
machine needs network access to the license manager machine when
turning coverage on and off
When the coverage shows 0% is there any indication that the
ctest_submit for the coverage step failed? (i.e. do you log the output
of ctest, and does it show anything about failing to submit?)
That's another type of intermittent network blip that I see, where
there's a successful local build,
No, they do not behave differently.
-j and --parallel are aliases for each other, using either one goes
through exactly the same command line argument processing code...
HTH,
David C.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Wow.
--
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 support the CMake community. For more
information on each offering, please visit:
CMake Support:
Not off topic at all.
Try start, test, submit, test, submit. Should work.
Start is the thing that writes a new time stamp tag, and all that follows
should be associated with the most recent start's tag.
HTH,
David C.
On Sep 5, 2014, at 5:07 PM, Biddiscombe, John A. biddi...@cscs.ch wrote:
You're welcome.
One caveat to mention with this sort of submit pattern (submitting
multiple build or test chunks to a single row on the CDash dashboard)
is that it messes up the incremental +n/-n
compare-to-previous-submission numbers of build warnings and errors,
and number of test passes
I wrote this blog post a couple years ago claiming one way to run a
dashboard on windows:
http://cmake.blogspot.com/2012/09/one-way-to-run-dashboard-on-windows.html
As with all such things, there are, of course, multiple ways to solve
the problem. At the time I wrote it, I trusted Visual Studio
No, but if you go to the Tests Query page, and set up a filter, you
can construct a URL for showing the failed tests with a given build
name and site name for the date in question... Almost as good.
Start here:
http://cdash.cscs.ch/queryTests.php?project=HPXdate=2014-09-08
(found from the
I don't think that's a good idea.
The Debug libraries are supposed to be non-redistributable. (At least
that used to be true... is it still true?) To Debug a VS-built project,
you have to run it on a machine with VS installed, so there's not a
compelling need to install the debug libraries
Let's see if anybody else chimes in with an opinion. I've already given
mine, and I don't think there's a good argument for making installing
the debug runtime libraries any easier than it already is.
You can certainly write a wrapper script around the existing CMake
I think (Ravi, correct me if I'm wrong) that they're transitioning to
CMake from a previously purely Visual Studio build system, and they're
writing some tools to validate that the builds are ending up the same.
So it's not really a problem for anybody -- I think he was just
looking for an
Is there a significant amount of output from make? What does make do if
it's running low on RAM?
ctest may be holding onto too much memory trying to process the
output if it's very large...
Just a thought -- worth a look, though.
D
--
Powered by www.kitware.com
Please keep messages
What happens when you run VS manually as the buildbot user? Any
warnings or errors?
--
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 support the CMake community. For more
If you are using SVN_REVISION with a specific revision number like
that, you can do:
UPDATE_COMMAND
because there is never any need to update after the initial checkout at
that revision.
If you then later change to another revision, the parameters to the svn
checkout (dowload) step
I still cant really make some arch specific ifdefs in my cmake
scripts using this approach.
That's the point of a multi-configuration, multi-architecture Visual
Studio solution: you defer choosing the configuration *and* the
architecture until build time.
No CMake time decisions are possible
No, the submit seems fine, but the value in the Coverage.xml looks
like
PercentCoverage0.00/PercentCoverage
ElapsedMinutes0.00/ElapsedMinutes
Which can't be.
However, the *-covbr.* and *-covsrc.* are generated with valid values.
Sounds like a bug in ctest then. There must be something
I am trying to configure the code coverage using the ctest script. I
took help from : http://www.cmake.org/Wiki/CTest/Coverage
That wiki page was mostly written in 2007 and 2009. You may want to
refer to something more recent than that, and something that's proven
to work, like an existing
As I said in my previous response, I don't know anybody who is using
Xcode on the Mac, and also successfully producing a gcov coverage build.
If I were you, I would:
(1) use gcov on a Linux build of your software for coverage
measurement, using the Unix Makefiles generator and the right gcov
My apologies. I take it back -- gcov apparently does work on the Mac
nowadays.
It is a ctest issue, then, and when using Xcode, ctest will need to
look in some additional locations for the coverage data files.
The source code is available -- patches welcome. :-)
D
--
Powered by
If you send some code, maybe somebody can spot something wrong with the code...
On Wed, Sep 24, 2014 at 9:57 AM, Richard Shaw hobbes1...@gmail.com wrote:
Ok, I have no idea what's going on.
I'm using configure_file to put the get_preresiquites cmake script in the
binary dir...
It's
INSTALL_COMMAND
should work. (Assuming you're doing ./b2 install as the BUILD_COMMAND...?)
Check out how the open chemistry project builds boost as an
ExternalProject as a reference point:
https://github.com/OpenChemistry/openchemistry/blob/master/cmake/External_boost.cmake
HTH,
David C.
On
Also, the default in cmake-gui is to prompt the user with the same
generator you used last time as the default value for 2nd and
subsequent runs of cmake-gui on any given machine by a given user...
So if you choose Win64 once in cmake-gui, and you always use
cmake-gui... you'll get it as the
Or, if echo is the thing that's supposed to see the \n, escape the
backslash and use \\n in CMake so CMake puts the literal \n in the
generated file instead of a newline.
HTH,
D
On Fri, Oct 3, 2014 at 5:27 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi Russell,
you might want to add VERBATIM
Switch the order of your add_subdirectory calls.
If your main depends on your library, then your add_subdirectory for
the library should be first, and then the one for your main which
depends on the first one.
HTH,
David C.
On Fri, Oct 3, 2014 at 3:55 AM, Jakub Zakrzewski jzakrzew...@e2e.ch
The documentation might be a little sparse, but file UPLOAD uses curl
in its implementation. So whatever protocols curl supports for
uploading to a URL should be supported by file UPLOAD, too. I know for
a fact it works with http, https and ftp. Is there some other protocol
you are trying to use
Does your dashboard script call ctest_read_custom_files after ctest_configure?
You should do that, as the CMake and VTK (and other) dashboards do:
What version of CMake are you using?
And on what platform?
And did you build it yourself, or are you using pre-built binaries
from somewhere?
On Wed, Oct 22, 2014 at 1:56 PM, jmerkow jmer...@gmail.com wrote:
Sorry for the delayed response.
Im trying to use sftp.
To test it out, I am doing
The new CMake web site looks fantastic! Even on my phone... Kudos to
everybody involved in making it look pretty after all these years of,
well, ahem, looking slightly less pretty...
However, on this page:
http://www.cmake.org/developer-resources/
The Dashboard icon is a broken link. 404.
Not sure there's a CMake question in here... Do you have a CMake
question, or did you mean to send these emails to another mailing
list?
Confused,
David C.
On Sat, Oct 25, 2014 at 2:33 PM, Colony.Three
colony.th...@protonmail.ch wrote:
Original Message
Subject: App Crash
I think your question about CXX_STANDARD is answered in the CXX_STANDARD
docs:
http://www.cmake.org/cmake/help/v3.1/prop_tgt/CXX_STANDARD.html
If you MUST have it, you can set this property to ON:
http://www.cmake.org/cmake/help/v3.1/prop_tgt/CXX_STANDARD_REQUIRED.html
(Although I've not used it
The Show My Changes menu item in the Tools menu gives you the -D command
line options for the things you've touched in the cmake-gui program...
HTH,
David C.
On Sat, Nov 1, 2014 at 12:16 PM, Saad Khattak saadrus...@gmail.com wrote:
Once I have configured and generated a CMake project, is
You will find a list of CMake Module Maintainers here:
http://www.cmake.org/Wiki/CMake:Module_Maintainers
If a module is not listed, it is not currently claimed. (Meaning
either nobody is currently maintaining it, or everybody is pitching
in a little bit as things important to them arise.)
This sounds pretty similar to the recent mailing list discussions
about the json file listing targets and properties of them at generate
time.
What would be the point? Just to look at the file as a human to see
what's in it? Or would you use it for something else...?
On Tue, Nov 18, 2014 at 9:25
This chunk:
target_include_directories(
mylib PUBLIC
# Headers used from source/build location:
$BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}
# Headers used from the installed location:
$INSTALL_INTERFACE:include
)
uses CMAKE_CURRENT_SOURCE_DIR, which already ends with /mylib.
Try:
cmake --build . --target examples
(where . represents the current working directory, and assumes
you're in the top level build tree...)
On Fri, Dec 5, 2014 at 5:46 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi all.
I'm converting a small Makefile-based project to CMake. The project is
No, I meant exactly what I said.
--target takes a CMake target name.
HTH,
D
On Fri, Dec 5, 2014 at 9:23 AM, Petr Kmoch petr.km...@gmail.com wrote:
I assume you actually meant 'cmake --build . --target example_dir', the name
of the directory. 'examples' is the name of the custom target; if
Paul,
Are you sure there's a problem using TARGET_FILE in your original context?
It seems to me it should work...
From
http://www.cmake.org/cmake/help/v3.1/manual/cmake-generator-expressions.7.html
:
$TARGET_FILE:tgt
Full path to main file (.exe, .so.1.2, .a) where tgt is the name of a
Can you run a command that executes one test case at a time, or do you
have to run all 50 when you execute the tests for a library?
ctest just runs whatever you give it with add_test -- if you want to
filter a collection of unit tests to run only a single unit test, then
the unit test framework
If you open the Tools Options dialog in Visual Studio, and
navigate to the Projects and Solutions Build and Run tab, what is
your maximum number of parallel project builds value?
For maximum parallel build capability, it should be set to the same as
the number of cores you have.
D
On Tue,
Ah ha! Back to the simpler approach with install(CODE!
Good idea, Nils.
Then you just need a stamp/sentinel file associated with running the
operation, and you can check it against your input.
For your comment line, you could use cmake -E echo to spit out a
comment before running the dSYM
The other way you could approach this, but which would not be as
simple would be to invent *your own* custom install target
(install_with_dSYM, or whatever name makes sense to you). Then you
could have that target depend on all the custom targets that build the
dSYM files. When you build this
I have two more suggestions for whoever takes on this work.
One: add a new CMake command add_unit_test_container (or
add_unit_tester or a better name ... ?) which names the DLL or
executable file containing the unit tests. Give it properties to
indicate how to extract a list of tests from it
Do you have a CTestConfig.cmake file in your source tree?
If you do, then ctest will load that instead of looking for the
DartConfiguration.tcl file in your build tree... Even if it's empty
because you don't submit to a CDash server, the presence of
CTestConfig.cmake in your top level source tree
This output:
On Sun, Feb 1, 2015 at 10:25 AM, Robert Ramey ra...@rrsd.com wrote:
Julien Jomier wrote
It seems to be here:
http://my.cdash.org/index.php?project=Safe+Numericsdate=2015-01-31
Note that CDash is processing the XML files asynchronously therefore it
might take some time for the
This output:
Submit files (using http)
Using HTTP submit method
Drop site:http://my.cdash.org/submit.php?project=Safe+Numerics
Uploaded:
/Users/robertramey/WorkingProjects/safe_numerics_xcode/Testing/20150201-0209/Build.xml
make: ***
It's only a chicken and egg problem if you constrain yourself artificially.
When you define a new unit test source file, there are two things you
need to do:
(1) add it to its executable
(2) write an add_test line that invokes that specific unit test
You could possibly encapsulate those actions
The best thing to do would be to make CTest aware of unit test
frameworks like this, and have it be automatic.
Support for cppunit, gtest and Catch (and any other popular ones)
would all be appreciated by many, I'm sure.
Got time to dig into ctest a little bit?
D
On Tue, Jan 27, 2015 at
I'm sure it's possible, as long as CDash can handle the flood of test results.
CTest is responsible for taking add_test (or whatever the new CMake
command will be called) calls and transforming them into Test.xml
files for sending to CDash. As long as you can read the output of
running the unit
Two ways to do this occur to me:
(1) wrap cmake with a two-line script that your project developers use:
@call cmake -G Visual Studio 12 2013
@call post-cmake.cmd
(2) do a file(WRITE ...) unconditionally somewhere in your
CMakeLists.txt file, and then introduce a custom command that
Have you considered having a superbuild and using
ExternalProject_Add to build the dependencies?
http://www.cmake.org/cmake/help/v3.1/module/ExternalProject.html
Excellent examples of using ExternalProject for a superbuild live in
the OpenChemistry and Slicer projects.
No, with the wrapper script technique, you'd have to train all your
developers to run the wrapper script whenever any CMake stuff
changes...
On Tue, Jan 6, 2015 at 8:39 AM, Petr Kmoch petr.km...@gmail.com wrote:
On Tue, Jan 6, 2015 at 2:29 PM, David Cole dlrd...@aol.com wrote:
Two ways to do
The easiest thing is probably to use the install(SCRIPT or
install(CODE signature of the install command rather than having a
build time custom command.
HTH,
David C.
On Sun, Feb 15, 2015 at 9:55 AM, Paul Smith p...@mad-scientist.net wrote:
In my Mac OSX builds I want to run dsymutil to
The The requested operation requires elevation. message indicates
some sort of permissions problem (admin privileges...)
Did you run VS and/or CMake as an admin one time, and then not as an
admin a second time...?
It should work with either all-non-admin runs or all-admin runs, but
you probably
What do you mean when you say I set CMAKE_ROOT to a directory ??
That should not be necessary, no matter how you're running cmake...
Is that an ENV var or a CMake variable you're setting somewhere?
D
On Wed, Jan 7, 2015 at 1:18 PM, david.k...@engilitycorp.com wrote:
A small correction: the
In general, I want all my unit tests to be built when I do a make
all, but I really don’t care if they are up to date for a make
install.
Are you sure you don't care? If your unit tests are out-of-date with
respect to what you are installing, and you have not run them against
what you are
There is no technical reason... But it seems to me there is a strong bias
toward single-architecture build trees in the minds of non-VS/non-XCode
developers.
There is rampant code like this in the world:
if(CMAKE_SIZEOF_VOID_P EQUAL 8)
# do 64-bit stuff at CMake time
else()
# do 32-bit stuff
1 - 100 of 332 matches
Mail list logo
