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
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
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 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:
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
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
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,
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
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
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
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:
Wow! Fantastic!
Thanks to Daniel, great work on this contribution... This is a ton of
tedious work, but it will be very useful. Thank you *very much*.
Two minor comments -- in the commit at the tip of this topic:
Thanks. Actually I think adding xz is incorrect anyway. We
support compressed tarballs, not arbitrary compressed files.
Therefore the list should be
7z|bz2|tar\\.gz|tar\\.xz|tgz|txz|zip
correct?
Well, then it should be tar.bz2, too. And since this is a regex
anyway:
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
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
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
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
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
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
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
301 - 332 of 332 matches
Mail list logo
