According to the docs, the INSTALL command uses the absolute path if
it is given as the DESTINATION, so it should work.
https://cmake.org/cmake/help/latest/command/install.html
Did you try using a double quoted string, instead of escaping the
space with a backslash?
I think this should work
omething like 5 or 6 years now...), but
still people write new find modules.
Thanks,
David C.
On Sun, Oct 1, 2017 at 11:52 AM, Alexander Neundorf
wrote:
> On 2017 M08 29, Tue 11:33:15 CEST David Cole via cmake-developers wrote:
>> That's correct:
>>
>> find modul
By manually deleting (or touching) the stamp file associated with the
earliest step you need to re-run.
ExternalProject is not for auto-detecting changes to stuff and
minimally re-running build steps. It's for static stuff that doesn't
change much.
Find the "-build" stamp file that's associated w
Sorry for the mis-statement. I stand corrected.
However, it is true that there are many find modules with some
differences in approach, and if you are using one, you need to read up
on the individual documentation of that particular find module.
Especially if you need to know how to tell it how to
That's correct:
find modules do what they want, and most do not pay attention to
CMAKE_PREFIX_PATH.
It's better to use a config file, but when you have to use a find
module, you have to dig in and figure out the right way to use each
one.
On Tue, Aug 29, 2017 at 11:25 AM, Robert Dailey
wrote:
Is there a ZLIBConfig.cmake file which find_package is searching for?
(i.e. -- somewhere under that directory does that file exist?) On
Windows the case won't matter, but on Linux, a find_package(ZLIB will
expect a case-sensitive match on a ZLIBConfig.cmake file.
If ZLIBConfig.cmake exists, it nee
Shouldn't the "/zlib" at the end be included in your CMAKE_PREFIX_PATH?
On Tue, Aug 29, 2017 at 11:01 AM, Robert Dailey
wrote:
> On Tue, Aug 29, 2017 at 9:56 AM, Brad King wrote:
>> On 08/29/2017 10:55 AM, Brad King wrote:
>>> On 08/29/2017 10:48 AM, Robert Dailey wrote:
CMAKE_PREFIX_PATH:
I suspect you are running a different cmake, not the one you've unzipped.
Type "where cmake" instead of "cmake --version" and Windows will list
the directories where it finds an executable named cmake. The first
one it lists is the one it is running when you type "cmake
--version"...
If you want
Yes, your code is a good example Marcus. It was one of the previous
suggestions on this thread which had example code setting
CMAKE_CONFIGURATION_TYPES.
I would recommend against setting this variable because in some places
in CMake code, it is used as an approximate proxy for whether or not a
mul
Very cool, Marcus. Thanks for the blog post.
Florian, when you "message(${CMAKE_CONFIGURATION_TYPES})" it is empty
because you are using a single-configuration CMake generator. Only
Visual Studio and Xcode (and possibly other) **multi** config
generators have a list of values in CMAKE_CONFIGURATIO
irectory "mapping" relative to that file
(which is down in the mapping/config dir)
On Tue, Aug 1, 2017 at 6:47 AM, Florian Lindner wrote:
> Hi,
>
> Am 01.08.2017 um 18:32 schrieb David Cole via CMake:
>> What source files include the header?
>
> It's in
What source files include the header?
Is one of them listed as a file in your project?
Does the **including** file exist at CMake configure time, or is it
generated later by a build step?
What do the lines of code that include the header look like?
CMake uses its own analysis of the source files t
You don't have to ask for a specific version. You can just do:
find_package(VTK REQUIRED)
if you don't really care what version is found.
Or if you need >= 7, you can do it like that and then check what
version was actually found, and error out yourself if it is too old.
HTH,
David C.
O
Very nice example. Does CMake have a place to put examples like VTK
does...? If so, where is it? And if not, it would be super useful to
start one somewhere "official."
However, one word of caution on the example. I know it was targeted at
Linux, and perhaps for a very simple case it's proper, but
When you convert that error code to hex, it's 0xc139, and if you
google that, you see it's an "entry point not found" error code.
Is something in the custom command trying to load a DLL that doesn't
have the expected export? Or perhaps trying to load a DLL of the wrong
architecture?
Or, there
Hopefully, somebody else doing something similar to what you're doing
will chime in here.
Seems overly complicated from an outsider's perspective.
If what you say is true ...:
"If 'copy_dlls' happens while 'B' is building, then it's possible the
post-build event run by B that deletes the 'libs' d
Seems to me the simplest thing to do would be to have copy_dlls depend
on nothing, and have package depend on copy_dlls and all the native
targets, and then tell your developers to run:
make individualTarget && make package
Either that, or introduce a packageIndividualTarget target for each
ind
I'm sorry, I misunderstood that you wanted it to run last regardless
of what target you are building. I was assuming you wanted it to
happen when you build the "all" target. I didn't think you wanted to
run it after any other *individual* target which you might specify.
I don't know of an easy way
The way I know how to do this is to add it last at the bottom of the
top-level CMakeLists.txt file, and then use add_dependencies to make
it depend on all other targets. (Or at least all other "leaf" targets,
which further depend on others, ... the sum of which is "all other
targets" besides the ne
>From the Windows command line, you would do it with 2>&1 after the command (2
>is stderr, and 1 is stdout). You could write your custom command as a batch
>file or bash script (unfortunately platform dependent) which uses this
>technique with a single command inside the batch file.
HTH,
David
Do give it a BINARY_DIR, but do NOT give it a BUILD_COMMAND. Giving it
an empty BUILD_COMMAND means "do nothing" for the build step and using
"cmake --build ./LibraryBuild" does not work unless cmake is in your
PATH, and with a Visual Studio solution, you also need to specify
"--config Release" or
Here's a bash script wrapper you could use with existing ctest. Save
it out to a file named ctest-two-labels.sh and then call it with bash
on Mac or Linux:
label1=$1
label2=$2
if [ -z "$label1" ]; then
echo "script takes two label arguments as input, missing arg 1"
exit 1
fi
if [ -z "$l
If the implementation is "run ctest in this build tree" and it
effectively simply does a "pushd $build_tree", runs, and then "popd",
then I don't see why anybody would object to it.
Although, a script wrapper would be completely trivial, and work with
existing ctest.
D
On Fri, Mar 24, 2017 at
This code:
https://github.com/Kitware/CMake/blob/master/Source/ctest.cxx#L139-L157
shows ctest will look for a CTestTestfile.cmake or DartTestfile.txt
file in the current working directory as soon as it starts. Except in
the case of processing a "--launch" directive, in which case, it
dispatches
Can you use Qt5? CMake 3.7 is typically built using Qt5: perhaps a Qt5
**requirement** has crept in since it's the commonly used one now.
HTH,
David C.
On Fri, Jan 6, 2017 at 10:41 AM, wrote:
> I'm running Ubuntu 14.04 and I'm trying to get the current version of CMake
> to run. (The apt-ge
This "compare" view on GitHub shows the difference between the
regular/upstream ninja and the Kitware patched ninja:
https://github.com/ninja-build/ninja/compare/master...Kitware:features-for-fortran
The ReadMe explains the high-level view, and says it is gradually
being worked into upstream
If you customize DOWNLOAD_COMMAND, you should also probably customize
UPDATE_COMMAND. If you are just using a fixed snapshot from some repo,
consider simply using a *.tar.gz snapped to that commit rather than
connecting to the repo at all. The GitHub "/archive/" URLs are perfect
for this.
However,
Using git like that is actually the perfect way to do it if you just want
to analyze it manually. I've actually done that with other projects source
trees when something seems to appear there even when doing an out of source
build... It's a great way to see what's changed (and how) easily.
You cou
Sounds like you should consider customizing the git clone with
DOWNLOAD_COMMAND. You can do anything you want as a customization...
HTH,
David
> On Oct 24, 2016, at 11:35 PM, Timothy Rae wrote:
>
> Thanks for the tip, but I'd rather it didn't fetch the documentation
> submodule at all, as th
"copy" should always overwrite.
"copy_if_different" will conditionally overwrite, only if the contents
of the two files are different.
If "copy" was not overwriting something when it should have been,
please send steps to reproduce the issue, because that would be a bug.
HTH,
David C.
On Fri
Does it work if you launch cmake-gui from the command prompt that
works for your "from the command line" scenario?
On Thu, Sep 22, 2016 at 1:58 PM, Michael Jackson
wrote:
> My combination is Windows 10 (Anniversary Update), Visual Studio 12 2013
> Update 5, Ninja and CMake 3.5/3.6.
>
> I launch C
There may be a hook at the CPack level you can implement, but I'd have to dig
to figure out what it is and if it even presently exists.
The easy thing to do would be to implement a custom target which does two
custom commands: the first the same as CPack (the built-in package target) and
the se
I suppose the obvious "use shorter paths and names" is not possible or hard to
enforce?
David
> On Sep 7, 2016, at 2:55 AM, Robert Bielik wrote:
>
> I have a problem with a VS 2015 project, where the build state path becomes
> too long:
>
> SeverityCodeDescriptionProjectFil
The best thing to do would be to add the feature to ctest, and
contribute to the CMake community.
I, too, use the "run this test first" and "that test last" technique,
and set up DEPENDS property values to ensure ordering when all tests
are run in parallel. However, as you noted, this does not wor
The code is not meant to be called. The "require += info_size" line is
to keep compiler optimizations from stripping out the info_size string
variable from the final executable.
This code is simply built, and then the resulting binary is scanned
for the string "INFO:size[],key[]" and then
Seems like you ought to be able to avoid this warning just by setting
ENABLE_EXPORTS to 0 or 1 ... If you're going to require 3.0, then use 3.0.
If you're going to use 3.5, then add the property to squelch the warning
and get the behavior you want.
D
On Wednesday, July 6, 2016, J Decker wrote:
Seems like you ought to be able to avoid this warning just by setting
ENABLE_EXPORTS to 0 or 1 ... If you're going to require 3.0, then use 3.0.
If you're going to use 3.5, then add the property to squelch the warning
and get the behavior you want.
D
On Wednesday, July 6, 2016, J Decker wrote:
The easiest way to do what you want here is to make a standalone
script (*.bat / *.cmd) that runs the commands you want and get it to
work without CMake involvement at all, and then simply use
execute_process to invoke that script.
You can pass arguments to it if you need to communicate informatio
Or just isolate it into its own CMakeLists.txt file in a sub-directory?
On Wed, Jun 1, 2016 at 8:34 AM, Nicholas Braden
wrote:
> Have you tried unsetting it after adding the executable in question?
> If that doesn't work, is it possible to make the MFX executable be the
> very last executable add
This file has an example use which executes after download and before configure:
https://github.com/Kitware/CMake/blob/master/Tests/ExternalProjectLocal/CMakeLists.txt
HTH,
David C.
> On Apr 8, 2016, at 6:39 PM, jagernico...@legtux.org wrote:
>
> Hi,
>
> my question is related to :
> http:/
Are you running a dashboard script (ctest -S script) when this
happens? Or calling ctest directly with other arguments?
If you are running a -S script, you can specify the configuration to
build and test in the script itself with the CTEST_CONFIGURATION_TYPE
script variable. Read the docs here on
A multiple folder approach will be very difficult.
The basic assumptions are:
- On Windows, the "one executable path" is the destination path to
which to copy all of the DLLs that need to be copied, so they all end
up in the same directory. (You'd have to have multiple copies in
multiple location
"A single pair of square brackets with ; inside have also long been
used to designate registry [key;value] pairs on Windows."
http://stackoverflow.com/a/36085151/236192
HTH,
David C.
On Fri, Mar 18, 2016 at 8:21 AM, Allen Barnett wrote:
> Hi Petr: You're right! If I rename "c" to "c]", it tre
If you include those files in the source list for a library, executable, or
custom target, they should show up in IDE projects, and they should be ignored
by Makefile type projects. Have you tried that?
David
> On Mar 7, 2016, at 6:34 PM, Eric Wing wrote:
>
> I have a bunch of .cmake support
It was designed originally with the assumption that all the
executables in a bundle are in the same directory. If you violate that
assumption, I don't think you can count on it to do the right thing
100% of the time.
If it works for you calling it multiple times with deepest first, then
maybe you
Newer versions of Visual Studio install a git, too, for their source
control integration features. Which git is CMake using, the one you've
installed or the one Visual Studio installed?
On Wed, Mar 2, 2016 at 12:45 AM, Kevin Brightwell
wrote:
> I've been having great success with using External
Do you need to do it indirectly through a variable like this?
If you just use:
INSTALL_COMMAND ""
directly in the ExternalProject_Add call, it will work.
If you really need to do it indirectly, there's probably a way, but it
will also probably be more confusing for people reading the code in
t
I can't think of a reason why we would not whitelist the FOLDER property...
Unless somebody else chimes in with one, perhaps you could submit a
proposed patch to whitelist it?
D
On Wednesday, December 30, 2015, Klaim - Joël Lamotte
wrote:
> The following CMake script:
>
> cmake_minimum_re
If BitDefender is quarantining those files, I would suspect the compiler you
are using has somehow become virus-infected...
What does BitDefender say if you ask it to analyze your compiler *.exe?
Maybe you should run a full scan of all the drives you are using here...
HTH,
David
> On Dec 29
Not only is it possible ... it WILL happen if you use the Microsoft
C++ compiler and try to mix and match Release and Debug compilation
units.
The MS compiler has some very nice memory tracking facilities built
into the Debug runtime libraries, but it is accomplished via different
structs for Debu
Build the second thing as an ExternalProject, too, and use the DEPENDS keyword
to make it build after the first thing.
Don't try to mix-and-match external projects and non-external projects in the
same CMake configure... It's just too much work to get things working in a
reasonable cross-platfo
I've got a Debug build of current 'master' on Windows, and the problem is
also evident with my build:
C:\dev\dcole\tmp\variable_watch_problem\b1> "C:\dev\repos\My Tests\cmake
Win32-ninja-cl12-Debug\bin\
cmake.exe" -G Ninja ..
-- The CXX compiler identification is MSVC 18.0.31101.0
-- Check for wo
Out of curiosity, what output do you get (with 3.4.1) when you comment out
your call to variable_watch? Do you still get error output, but without
strange symbols in it? Or is there no error output in that case?
On Thursday, December 10, 2015, Yves Frederix
wrote:
> Hi all,
>
> I am experiencin
$ cmake -E copy_directory foo bar/foo
?
On Mon, Dec 7, 2015 at 4:53 PM, Robert Dailey wrote:
> I have a custom target which runs a command similar to this:
>
> $ cmake -E copy_directory foo bar
>
> The problem is that the contents of "foo" are copied inside of "bar",
> instead of it creating a
You're welcome.
I see you have ${file}-2.h5m in only one place, though... Is that a
leftover, or is the other reference to -2 just omitted from your example...?
Cheers,
David C.
On Monday, November 23, 2015, Nico Schlömer
wrote:
> Thanks David for your explanations. I've now reached a good
You don't. You just assume all relevant targets have already been built by
the time you run the tests... There's no such thing as a test from
an add_test call depending on a target.
There **is** a dependency, of course, if you are using one of the build
products in your test, but it's assumed that
Use ALL to include your custom target in the default build of all.
https://cmake.org/cmake/help/v3.4/command/add_custom_target.html
D
On Sunday, November 22, 2015, Nico Schlömer
wrote:
> I was under the impression that if I don't explicitly build a target, it
> won't get build. Perhaps I'm w
The DEPENDS property of a test is meant to ensure test running order in the
case of parallel testing... It simply ensures that one test runs before
another. It is not connected to the build system at all. It's different
than target dependencies.
D
On Sunday, November 22, 2015, David Cole wrot
What do you mean by "depend" in this case? All libs and exes should be
built during a "make" or "make all" or "make install" ... And all that
should be done before any tests get run.
Simply typing "ctest" to execute all the tests never does any building. The
assumed workflow is that you build stuf
Did you try using full path names for the add_custom_command file names?
And the NAME/COMMAND form of the add_test command?
Also, I've always found custom commands to work best when they're
associated with a target. And if it was part of a target you could make the
target depend on the external d
Looks to me like it might be (I'm hopeful) working at ignoring the
line which matches the expression ".*vcl_deprecated_header.h.*" ...
But then, the following line is:
# warning "deprecated"
Since that line does not match any of your expressions, maybe that's
the one triggering this warning
Does your ctest -S script call ctest_read_custom_files
https://cmake.org/cmake/help/v3.4/command/ctest_read_custom_files.html
after ctest_configure?
On Thursday, November 5, 2015, Rashad M wrote:
> Hello all,
>
> I have CTestCustom.cmake.in file in source tree with the following
> contents
>
>
What version of Visual Studio do you have installed?
On Thursday, November 5, 2015, Nikita Barawade <
nikita.baraw...@einfochips.com> wrote:
> Hi,
>
>
> New to cmake utility,
>
> I am trying to build sample program given here
> https://cognitivewaves.wordpress.com/cmake-and-visual-studio/ with V
Oh wait, I read it wrong...
Try ${} to get the value of the variable. (It contains a file name, right?)
D
On Saturday, October 31, 2015, David Cole wrote:
> Because you're giving DEPENDS as a target name, this is only an ordering
> dependency, stating that the command should run after the t
Because you're giving DEPENDS as a target name, this is only an ordering
dependency, stating that the command should run after the target is built.
But not necessarily re-build whenever the target is re-built...
If you want to re-run the command based on a file changing instead, then
use the full
CMAKE_BUILD_TYPE is not typically used/useful with the Visual Studio
generators. You may want to look into using the CMAKE_CFG_INTDIR
variable instead.
https://cmake.org/cmake/help/v3.3/variable/CMAKE_CFG_INTDIR.html
On Tue, Oct 27, 2015 at 8:06 AM, Holzinger, Axel (ALC NetworX GmbH)
wrote:
>
The "-1" bz2 files are for Cygwin...
Try the plain old .tar.gz instead.
David
> On Oct 1, 2015, at 7:51 PM, Damian Rouson
> wrote:
>
> All,
>
> Could someone advise me on building CMake from source on OS X 10.10.5
> (Yosemite)? At the bottom of this email is the tail of the output from th
This message is sent when an unparseable xml file is submitted to CDash.
The email says the contents are as follows, with nothing (the empty string)
following... So, usually, this is some bot sending garbage to your CDash
url. There is nothing for you to do, but ignore these. If they are too
freque
Find_library results are cached. If you want to re-find a potentially moved
library every time you run, you would have to unset the cache variable
prior to finding it.
D
On Thursday, August 20, 2015, Ette, Anthony (CDS) <
anthony.r.e...@controlsdata.com> wrote:
> Ok so I’ve got this going now (
A totally reasonable suggestion. Patches welcome. ;-)
On Tuesday, August 11, 2015, Dan Kegel wrote:
> Aha. Well, how about sanity checks on the names of the properties?
> Maybe a new policy could be added that property names have to be
> declared (and the ones supported by cmake itself would b
The final args to set_target_properties are any number of name/value pairs:
http://www.cmake.org/cmake/help/v3.3/command/set_target_properties.html
The only thing we could do there is look for an even number of args, and
catch possible problems half the time... I'm not sure if there are any
restr
It's in the bug database here:
http://www.cmake.org/Bug/view.php?id=15134
Not sure how easy it would be to fix...
Also, this CLOSED bug is in there (and some related issues):
http://www.cmake.org/Bug/view.php?id=10072
D
On Fri, Aug 7, 2015 at 12:37 PM, Johannes Schauer wrote:
> Hi,
>
> Quot
Put your source in a sub-directory. CMake simply does not work at the
root of a drive letter on Windows. CMakeLists.txt MUST be in at least
one sub-directory underneath a root drive letter path.
HTH,
David C.
On Fri, Aug 7, 2015 at 5:08 AM, Johannes Schauer wrote:
> Hi,
>
> I am trying to bui
There's nothing wrong with that approach, per se, it simply "doesn't
feel natural" to Xcode and Visual Studio users.
Xcode and Visual Studio users building modern apps for multiple
targeted platforms (phone, tablet, simulated phone/tablet, desktop,
other) are used to switching the target platform
You could argue bug or feature depending on your point of view. (I'd lean
toward bug, as it is rather unexpected...) However, it has been that way
for quite some time, (ever since function was added?), so it may require a
new policy to fix, since some function calls from inside functions may be
acc
OK, I finally have a build of boost I can rely on which enables me to
try this out for you again.
Using the following source tree, I am able to get a successful build &
test of Safe Numerics, other than a couple of warnings, and it
actually submits to the CDash dashboard, no problem.
Source tree
Get the list of all files, loop over them, and filter out the ones
that DO have the string in the name ...?
On Thu, Jul 30, 2015 at 4:05 PM, Crast, Nicholas
wrote:
> All,
>
>
>
> This seems like a pretty simple task, but I cannot figure out a good way to
> do it. I want to get a list of all fil
json is SOOO much sexier than XML. ;-)
On Thu, Jul 30, 2015 at 10:10 AM, Dan Kegel wrote:
>>> The big selling point would be the ability to introduce arbitrary
>>> front-ends to CMake, not just CMakelists.txt. Every developer could
>>> choose an input language that suits their pro
And I wouldn't give up just yet on building support for this into
CMake, if not building the entire thing into a future CMake. Perhaps
there are valid objections, or perhaps people just need convincing.
D
On Wed, Jul 29, 2015 at 8:51 AM, Nagy-Egri Máté Ferenc wrote:
> Hi Nico,
>
> thank you for
This all seems like a very good idea, and also like it will take an
enormous amount of time and effort. I'd like to help, but I have quite
limited available time these days. Let us know if there are specific
things you need help with in advancing towards an implementation of
these ideas.
David C.
Interesting idea.
I can say for sure one of the reasons we didn't take this approach when we
first built ExternalProject was to avoid spending significant time on
ANYTHING during the CMake configure of the main project. Deferring
everything time-consuming to build time, after the configure step, w
I think
http://www.cmake.org/cmake/help/v3.3/variable/CMAKE_CURRENT_LIST_FILE.html
is exactly what you're asking for, and will work in most contexts you're
thinking of. (Configuring from a top level or sub-directory CMakeLists
file, in an included file, running a CMake -P script file...)
The only
CMake only puts projects (libraries, executables, custom targets) inside of
solution folders. There's currently no way to add an individual file in
them directly.
D
On Thu, Jul 23, 2015 at 11:24 AM, Andrei Porumb
wrote:
> Hello Parag,
>
>
>
> I am very sorry to say that your
However, be aware of two things if you do use FORCE:
If CMAKE_CXX_FLAGS_RELEASE already contains "-xHost" you will be
appending it *again* each time CMake is run in a given build tree...
So you may want some "if(NOT CMAKE_CXX_FLAGS_RELEASE MATCHES
"-xHost")" logic in there as well.
Also, using FO
Nope.
CMake has no way of knowing whether you have logic in the lower level
CMakeLists file which affects later included projects, or which might
even possibly affect global (top level project) CMakeCache settings.
Without adding facilities to track such interconnections, the entire
tree from the
Try putting ${FOO_HEADER_FILES} in the add_library call, too.
I reproduced this by adding a file, with **ANY** name, to the
PUBLIC_HEADER list of the
[CMake/Tests/Framework/CMakeLists.txt](https://github.com/Kitware/CMake/blob/master/Tests/Framework/CMakeLists.txt)
file... but NOT adding it to the
Are you saying the file does not exist in the installed framework, or
that you do not see "copying Foo.h" in the install output ...? This
seems very unlikely. The header files are supposed to be in the
framework in the build tree, and the built framework in its entirety
is supposed to be recursivel
The split technique should be able to help in this scenario as well,
because for the second project, which builds the code downloaded by the
first project, you can specify a different SOURCE_DIR value... (A sub
directory of the first project's source dir, for example.)
It would be nice if EP stuff
I have adopted the technique of splitting a project into two
ExternalProject_Add calls, the first of which is named
"download-${projectName}" with empty configure, build and install
stages, and the second of which is named ${projectName} with an empty
download step (using DOWNLOAD_COMMAND "").
The
Most of the variables that have a per-config variation on the name end
with "_" ( see the page documenting CMake variables, and
search it for "config" to get a sense of which variables these are...
http://www.cmake.org/cmake/help/v3.3/manual/cmake-variables.7.html )
-- s, if you do prepare any
It's just something you can't change without wiping the build tree
entirely. It should probably actually produce an error or warning of
some sort to avoid confusion such as this...
D
On Tue, Jul 14, 2015 at 11:01 AM, Paul Smith wrote:
> We have a situation where people are sometimes wanting to
A few more ideas:
The other "no need to modify CMake" way to achieve this (although it
may be considered "too ugly" or non-ideal by some) would be to force
the use of a single configuration per build tree, and use the proper
value for CMAKE_INSTALL_PREFIX in each build tree.
Your developers may
I think this should be achievable somehow with CMAKE_INSTALL_PREFIX
set to "/parent_dirs" and then using appropriate DESTINATION and
CONFIGURATIONS arguments to the CMake install commands.
Have you tried using the CONFIGURATIONS args to the install command?
On Mon, Jul 13, 2015 at 10:26 AM, Cli
I cloned your project [Safe
Numerics](https://github.com/robertramey/safe_numerics) to try to help
you out by attempting to reproduce this problem.
I see the most recent activity is in the "policies" branch, but I
don't see anything in the whole repo, in either 'master' or 'policies'
branches that
pped your source tree for -j yet?
>>>
>>>
>>> On Thu, Jun 18, 2015 at 3:17 PM, Michael Jackson
>>> wrote:
>>>> I will have to admit that I don't pretend to completely understand the
>>>> CMake file that I am using as I started with something from VTK and
>&
gt;
>
> Thanks
> Mike Jackson
>
> On Jun 18, 2015, at 3:08 PM, David Cole via CMake wrote:
>
>> Are you using Eclipse or Kate?
>>
>> Did you do a grep -E "\-j" on all of the files included by the script
>> that drives the build? (And in your source
Did you read through the pointed to stack overflow question and answers?
Is the information there misleading or incorrect?, ... because it
seems to say there is a way to do it with MSVC...
On Thu, Jun 18, 2015 at 3:16 PM, Robert Dailey wrote:
> On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew w
Are you using Eclipse or Kate?
Did you do a grep -E "\-j" on all of the files included by the script
that drives the build? (And in your source tree?)
The only -j possibilities that look likely in CMake itself are shown
in the git grep results from a CMake checkout:
$ git grep -E "\-j"
Modules/
Is there a MAKEFLAGS or CTEST_BUILD_FLAGS in your environment?
Where does the -j16 come from? (CTest should not be injecting that
unless you are telling it to somehow, so it either comes from one of
your scripts, or your environment...)
grep for just "\-j" -- the value 16 may come from a variable
I think I have seen this behavior in pure (non-CMake-generated) VS
projects... Perhaps it's simply a Visual Studio issue, and has nothing
to do with CMake.
D
On Fri, Jun 12, 2015 at 7:55 AM, Roman Wüger wrote:
> @kgt: Thank you for this great hint. :-)
> I had overlooked this button in Visual St
1 - 100 of 240 matches
Mail list logo
