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
Why are you holding back so much from giving us your real opinion of
Cygwin? :-)
Sorry about that, I'll have to try harder ;-)
Seriously though, I wonder if some of your complaints have an answer.
I'm sure they do.
Also, I think it is important for Windows users to have access to
I finally got it working.
Good!
- I ditched Cygwin. (But I learned that CMake later on for Unix
Makefiles complains about Cygwin sh.exe being in my path, and
uninstalling Cygwin is kind of hard.)
Good!
The difficulty of uninstalling it, and the difficulty of replicating a
cygwin
#
# CMakeLists.txt
#
# PROBLEM:
#
# This file demonstrates a problem with CMake 3.0 and Visual Studio
# compiler x64 builds... If configured for a build with the x64
# compiler, CMake will hang until user intervention with a
# cmTryCompileExec123...789.exe has stopped working
# crash dialog.
#
#
Would you also be satisfied if the crash dialog was disabled in the
try_run()?
That is done for ctest by cmCTest::BlockTestErrorDiagnostics().
Sure, as long as the try_run doesn't hang, and indicates failed run
in the run result.
I'm easy.
D
--
Powered by www.kitware.com
Please keep
Nice literate programming!
Thank you.
--
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
If you *really* wanna save on typing:
alias c=''\''C:/Program Files (x86)/CMake/bin/cmake.exe'\'' -G
Ninja'
(or the equivalent on your machine...)
:-)
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
If BundleUtilities works for you (sounds like it doesn't, though...),
you can easily add a call to the script as a custom build step instead
of doing it at install time. It's just a cmake script to run, so you
can run it anytime you like...
HTH,
David C.
--
Powered by www.kitware.com
I am currently in this unholy trinity of needing to use Android on
Windows through Cygwin.
Rule: NEVER use cygwin on Windows. Period.
If something says you have to use it for some reason, call bullsh*t,
and refuse to do it. Figure out what you have to do to avoid it.
:-)
--
Powered by
What is returned if string(FIND) matches a substring, and what is
returned if it doesn't match anything?
The documentation says:
http://cmake.org/cmake/help/v2.8.12/cmake.html#command:string
http://www.cmake.org/cmake/help/v3.0/command/string.html
string(FIND string substring output variable
Is it possible to invoke a script function as part of a target?
No, because the variable values are all gone after CMake finishes
running. And the custom build targets do not run until later at build
time.
I have a build step where I need to process a bunch of variable
values before
Are there some good examples of why one would use bracket arguments?
I think one of the major use cases for bracket arguments is in
file(WRITE so you can embed literal python code (or Lua, or
javascript, or ...) directly in the argument to the file command and
have a section of your CMakeLists
The cache is telling you:
//No help, variable specified on the command line.
If you want the help string from your sources to appear in the
CMakeCache.txt, then don't specify a value for it on the command line...
Delete the cache, and try again without giving the arg on the command
line,
Chad,
What is the value of CMAKE_BUILD_TOOL?
i.e. output of:
message(STATUS CMAKE_BUILD_TOOL='${CMAKE_BUILD_TOOL}')
Why are you using ${CMAKE_BUILD_TOOL} anyhow when the command lines
you're giving will only work with 'make'?
--
Powered by www.kitware.com
Please keep messages on-topic
It's allowed, but it will have the value of target_name from the
context of the CMake configure process. (i.e. ${target_name} is
evaluated at configure time, and then the evaluated result is what's
used at generate time within the generator expression.)
HTH,
David C.
--
Powered by
Hi everybody there,
Subject says it all. See the attached patch please.
(Didn't care enough to leave hg for git to generate the patch. Sorry.)
FILE_PATH is likely to contain C: or some other drive letter on
Windows. It is therefore unsuitable for using to construct a sub-path
underneath
Maybe I'm missing something. Is it guaranteed that all callers of
PROTOBUF_GENERATE_CPP will pass non-full-path names for the .proto
source files?
If so, then I retract my statement. But I don't think you can guarantee
that.
David C.
--
Powered by www.kitware.com
Please keep messages
... Long story short I think it is safe to assume ...
It is never safe to assume anything. I don't have personal experience
with protobuf
But in general, inputs to CMake are allowed to be full path or not, and
when not, they're usually treated relative to CMAKE_CURRENT_SOURCE_DIR.
This topic itself looks simple enough, and it fixes the problem you've
observed. I guess my question is, are there still other instances of
this problem, and why wouldn't we want to do this for inputs *not*
specified by full path? Shouldn't we infer the correct full path at
add_custom_command
Where there's a will, there's a way...
Lucky for you CDash is open source.
:-)
--
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
However, if the target of your project IS a static library that you
supply to customers for integration into their toosl, you NEED to
supply the pdb otherwise they are stuck getting the “pdb not found”
warning message.
Rather than having a separate pdb file, for debug static libraries, you
Hi Tim,
I just created a test project t2 with Xcode itself, and in the
projects source file t2-Info.plist, I added a Get info string key
with a value of This is the ${CONFIGURATION} build.
Then, after I build the Debug config, and inspect the generated bundle,
the Info.plist inside of it
Thanks David, but my cache entry for MY_VCVARSALL_BAT looks fine
already
...
So any .. has been resolved automatically by find_file, even
without explicitly specifying ABSOLUTE :-)
...it does not seem to make a difference in this case. Right?
Right. Then you are good to go. I have not relied
Does CMAKE_CXX_COMPILER always provide the full path name of the
compiler, when we use the current version of CMake (2.8.12.2)? In the
past it did not, apparently, as a CMakeCache.txt file generated by
CMake 2.8.8 simply had cl as compiler file path
I think now it does, but I'm not 100%
Also, one more comment on your technique:
If you use get_filename_component in conjunction with paths that
contain .. or Windows-style component separators (\), you can
always clean up the resulting string with the ABSOLUTE argument to
get_filename_component. It will collapse any /../ or /./
How about:
if(EXISTS $ENV{VS110COMNTOOLS}../../VC)
get_filename_component(VC11_DIR $ENV{VS110COMNTOOLS}../../VC
ABSOLUTE)
endif()
if(EXISTS $ENV{VS120COMNTOOLS}../../VC)
get_filename_component(VC12_DIR $ENV{VS120COMNTOOLS}../../VC
ABSOLUTE)
endif()
message(STATUS
In CMakeCache.txt, for a Visual Studio based build where C and/or C++
has been enabled:
//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual
Studio 11.0/VC/bin/cl.exe
//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual
Studio
ExternalProject: Set LABELS property to targets
his is useful for using CDash subprojects.
ExternalProject: Set FOLDER property to targets
This is useful when using the USE_FOLDERS global property
Seems like something this simple is not quite flexible enough to make
it worthwhile. You could
I'm always happy to learn something new. How would you manage to make
the following if statement trigger?
set( arg value)
if ( ${arg} STREQUAL TOTO )
message ( arg equals 'TOTO', and arg equals 'value' )
endif()
By having a variable named value that you didn't know about...
This
A simple example:
Sln1/CMakeLists.txt --
cmake_minimum_required(VERSION 2.8)
project(project1)
ADD_LIBRARY (project1 STATIC main.cpp)
Sln2/CMakeLists.txt --
cmake_minimum_required(VERSION 2.8)
So even though the cmake binary can no longer generate the html and
manpage documentation itself it is still available.
To search the 3.0 rc4 help for find package, you can:
http://www.cmake.org/cmake/help/v3.0/search.html?q=find+package
And if you don't trust the web based search, you
You sure? When I checked, this did not work. Also, the following
gives me a syntax error:
set ( foo Evil!)
message( ${ foo})
But you *can* still do it indirectly (even with the 3.0 RCs):
set ( variable with spaces Evil too!)
set (varname variable with spaces)
The way I’m doing this now is the following:
a) I edit the CMakeList.txt file(s) and follow
the procedure to create an Xcode IDE project.
This project contains a bunch of targets
including ALL_BUILD, RUN_TESTS, and
Experimental - among others
You should not have to
fyi...
see also:
https://github.com/Kitware/CMake/pull/31
http://public.kitware.com/Bug/view.php?id=5145
http://public.kitware.com/Bug/view.php?id=14306
http://public.kitware.com/Bug/view.php?id=10901
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hey guys,
Here's an example script that may (or may not!) illuminate things
somewhat:
https://gist.github.com/dlrdave/10977804
I think the main point of having VARIABLE in the get_property signature
is to test whether or not a variable is SET or DEFINED with the uniform
api of
Hmm..
It is a little bit confusing for newcommers that you can not do
simple comparision for text word
if some variable with this name exists.
Oh, it's confusing and confounding to old-timers, too... :-)
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Here's a guess:
For dashboard submissions, some prefer to see *as many errors as
possible* at once in one go, so as to have the least turnaround time in
fixing errors on a remote system without having direct access to that
system.
To accommodate such a preference, the default flags have
On 6. Apr 2014, at 16:48, David Cole dlrd...@aol.com wrote:
The patch says it's based on
9dadcae57bc8545d1af66ede4c91c06eaa49f9d6 but I
don't see that commit in CMake 'master' or 'next' branches..
Where is that commit?
It's my local commit containing the changes. I don't think I have
The patch says it's based on 9dadcae57bc8545d1af66ede4c91c06eaa49f9d6
but I don't see that commit in CMake 'master' or 'next' branches..
Where is that commit?
Thx,
David C.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
From: Dan Kegel d...@kegel.com
Sent: Mon, Mar 31, 2014 10:20 am
On Mon, Mar 31, 2014 at 7:13 AM, David Cole dlrd...@aol.com wrote:
It will be cool to be able to build Metro apps using CMake.
Well, aside from the obvious problem :-)
Well .. obviously. ;-)
--
Powered
From: Dan Kegel d...@kegel.com
Sent: Mon, Mar 31, 2014 10:20 am
On Mon, Mar 31, 2014 at 7:13 AM, David Cole dlrd...@aol.com wrote:
It will be cool to be able to build Metro apps using CMake.
Well, aside from the obvious problem :-)
Well .. obviously. ;-)
--
Powered
Thanks for working on this. It will be cool to be able to build Metro
apps using CMake.
One thing I think is crucial here is to include somewhere an example or
test project that actually builds a Metro app, and shows how you have
to construct the CMakeLists for it, and any special
Thanks for working on this. It will be cool to be able to build Metro
apps using CMake.
One thing I think is crucial here is to include somewhere an example or
test project that actually builds a Metro app, and shows how you have
to construct the CMakeLists for it, and any special
Well, that sounds like the perfect way to use ExternalProject.
But why do you want to show the sources in Visual Studio? Just for ease
of looking at them?
As I said in my earlier reply... even if we showed the sources, editing
them would not trigger a rebuild of the external project. The
/install in
there, then go back to your containing project, and it's already up to
date.
To each his own... Good luck.
HTH,
David C.
-Original Message-
From: NoRulez noru...@me.com
To: David Cole dlrd...@aol.com
Cc: cmake cmake@cmake.org
Sent: Wed, Mar 19, 2014 9:48 am
Subject: Re: [CMake
Why do you want to do that?
The ExternalProject will not rebuild correctly when you modify these
source files... Unless you are forcing the build step to run every
single time.
You are using ExternalProject as if it were NOT external. Why not just
use add_subdirectory instead and have an
629037c
Author: David Cole dc...@neocisinc.com
AuthorDate: Mon Mar 17 08:52:46 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Mar 17 08:52:46 2014 -0400
Merge topic 'fix-out-of-date-CTestTestMemcheck' into next
629037c3 - Prevent unnecessary rebuilds
I do this to avoid using CMAKE_CURRENT_LIST_DIR in projects that must
still work with older CMake versions:
get_filename_component(_self_dir ${CMAKE_CURRENT_LIST_FILE} PATH)
After that call, the variable _self_dir has equivalent content to the
present-day CMAKE_CURRENT_LIST_DIR.
If a custom command fails, it stops the build. It's equivalent to a
failed compile of a source file.
If you want to avoid it, then wrap the command in a script, and make
the script eat the error, and return success to its caller.
If you don't care if the command fails, then why are you
You can search the bug tracker http://public.kitware.com/Bug for known
CMake bugs related to Xcode... I don't recall anything like this being
reported recently.
What version of Xcode?
What error message do you get when trying to open the project with
Xcode?
D
--
Powered by
Anybody else out there using Xcode 5.0.2 with CMake yet?
Perhaps open a bug report, and attach the generated Xcode project
files. Or send a minimal CMakeLists.txt file that reproduces the
problem. Does it happen with the very simplest CMakeLists file? (For
example, the one from the tutorial
Sure it should -- can you edit the wiki page, and correct it?
I don't have an account to edit the WIKI, so it might be faster
if somebody who already does have an account does so.
Actually, I never should have sent my request.. :-)
Chuck Atkins already had done it and replied that it
That's just the quick brain dump version. If necessary, I can
actually
look at old commits, or the current code to try to refresh my memory.
I think that's needed. Can you do that research into the commits and
discussion?
Please see the results of my research (aka, old commits detective
How can I structure my cmake file to avoid
this double build?
Put the custom command in a custom target, and make the libraries using
the generated file depend on the custom target.
That works, even for parallel builds.
Google around for examples and similar advice. You'll end up using
Right, so what Sean was saying is:
standard library version-to-version incompatibilities == ABI
instability
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake
#1. The cmake roadmap informs me that 100% of version 3.0
is complete. Any news on when this will be released?
Soon:-)
(Although, disclaimer: I'm not responsible for it anymore, so I can't
be more precise than that...)
#2. How does the development team decide which issues
are
That's just the quick brain dump version. If necessary, I can
actually
look at old commits, or the current code to try to refresh my memory.
I think that's needed. Can you do that research into the commits and
discussion?
I know it's been a week now I'm still getting to this. Will
Should I file this as a bug in the issue tracker then?
Sure. Especially if you have an easy way to reproduce. (Either
reference an external, publicly available project we can just
build and get it to happen, or attach a CMakeLists that
demonstrates the issue if possible.)
That way, we can
Should I file this as a bug in the issue tracker then?
Sure. Especially if you have an easy way to reproduce. (Either
reference an external, publicly available project we can just build
and get it to happen, or attach a CMakeLists that demonstrates the
issue if possible.)
That way, we can
What does your call to ExternalProject_Add look like now?
--
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
When you give a git repo for ExternalProject, it will *always* execute
the UPDATE_COMMAND by default. And then, all the steps after update
will re-execute since update re-ran.
If you want to use a git repo, but prevent this behavior, you can say:
UPDATE_COMMAND
to eliminate the default
To: Marcel Loose lo...@astron.nl
Cc: cmake cmake@cmake.org; David Cole dlrd...@aol.com; Stephen
Kelly steve...@gmail.com
Sent: Mon, Feb 3, 2014 11:51 am
Subject: Re: [CMake] include_directories(...) versus
set_directory_properties(PROPERTIES INCLUDE_DIRECTORIES ...)
On 01/30/2014 03:08 AM, Marcel
Awesome, welcome!
Seconded!
Thirded!
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to
Attached is a patch for the ExternalProject test that simply passes
an
empty list.
Thanks, that's completely reasonable for a first-time contributor to
CMake. I understand it's not easy to jump right in and understand how
all the tests operate...
I'd like to pass further testing, i.e.
This approach should work... *but* you should always use the full path
name to any custom commands. So the runthis.bat should be:
${CMAKE_CURRENT_BINARY_DIR}/runthis.bat or SOURCE_DIR/runthis.bat
Glad you got it working with CMake, though.
-Original Message-
From: Rob McDonald
If all the tests pass for you locally, and you are pretty sure they
will all pass on other machines too, then you can do it whenever you
think it's ready. (Unless somebody else has given you feedback that you
need to address first...)
The primary thing is to monitor the Continuous dashboards
This looks like a reasonable patch to me (just by eye, have not tried
it personally). *Although* it would be even better if there were an
additional case added in the ExternalProject test that handles passing
in (1) an empty git submodule list, and (2) a valid list. Although,
unless you add
Why not just write your own batch ('buildit.bat') file that does:
call vcvarsall.bat
nmake
(or whatever the command to build in the VS command prompt is...)
And then your command to build is:
C:/full/path/to/buildit.bat
It's presumably in a Windows-specific chunk of your CMakeLists
I've got a batch file that does something like this to detect the most
recent available Visual Studio:
@rem ** Add Developer Command Prompt for VS2013, 2012 or 2010
environment:
@set _vsver=
@set _vs12env=%VS120COMNTOOLS%VsDevCmd.bat
@if %_vsver% equ if exist %_vs12env% set _vsver=12
@set
301 - 400 of 3692 matches
Mail list logo
