Well, sorry you found it tedious to go through those steps, but please
consider the flip side of the coin, too:
The wiki has actually been defaced/attacked by spammers in the past,
who have done some pretty silly things just to get the links to their
trash out there... So, the barriers to entry
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
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
There is a similar (old) feature request in the bug tracker for a
build button:
http://public.kitware.com/Bug/view.php?id=8260
See the commentary there when considering adding a button to cmake-gui...
D
On Thu, Feb 5, 2015 at 4:54 AM, Paul Anton Letnes p...@letnes.com wrote:
Hi!
I
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: ***
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
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
that it appears as if it was instead run
once for each test case?
I'm being fairly abstract here as I'm not sure of the implementation
details of CTest or if this is even possible. But it's a thought. Let
me know what you think.
On Wed, Jan 28, 2015 at 6:43 AM, David Cole dlrd...@aol.com wrote:
I
of is to
generate 1 test executable per CPP file that we write in our unit
tests (generally 1 CPP file per class that is unit tested). Any ideas?
On Mon, Jan 26, 2015 at 10:05 AM, David Cole dlrd...@aol.com wrote:
Can you run a command that executes one test case at a time, or do you
have to run all 50 when
, David Cole dlrd...@aol.com wrote:
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
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
This is a pre-built Linux binary that should work on that system, and
should include ccmake:
http://www.cmake.org/files/v2.8/cmake-2.8.8-Linux-i386.tar.gz
If you can't run it, it's probably because you're on an x64 box, and
you need the run the 32-bit exes and libs library -- hopefully
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,
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.
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
elevation error, same as before. Go figure.
David
-Original Message-
From: Karr, David A. @ EngilityCorp
Sent: Wednesday, January 07, 2015 12:47 PM
To: 'David Cole'
Cc: cmake@cmake.org
Subject: RE: [CMake] Unable to create project files with Visual Studio
2010 on Windows 7
I tried
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
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
This looks pretty reasonable to me. From Rob's initial email, I
thought it sounded like there was some sort of backward compatibility
problem, but looking through the code, it seems like everything should
all work the same for projects that aren't changing. Was I
misunderstanding about
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
Looking at our own internal test suite usage of RANDOM_SEED leads to
the conclusion that we do not verify the sequences produced when
actually using RANDOM_SEED..
So, from our point of view, we don't really care about what effect
RANDOM_SEED has for our test suite. But I think we do still
Sie:
On Thu, Dec 11, 2014 at 14:41:36 -0500, David Cole via cmake-developers
wrote:
Yes, setting an explicit seed should make subsequent calls to random
be deterministic...
Well, *we* want that, but I don't think that OpenBSD is making an
*awful* decision here.
Even if you want
as
the expected test results account for any differences that do exist,
the goal can still be satisfied: predictable results.
thx,
D
On Sat, Dec 13, 2014 at 1:05 PM, Ben Boeckel ben.boec...@kitware.com wrote:
On Thu, Dec 11, 2014 at 14:41:36 -0500, David Cole via cmake-developers wrote:
Yes
Yes, setting an explicit seed should make subsequent calls to random
be deterministic...
On Wed, Dec 10, 2014 at 9:50 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Am 10.12.2014 15:38, schrieb Ben Boeckel:
Hi,
It appears[1] as though OpenBSD has changed srand and rand which we use
in CMake for
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
in the solution.
On Fri, Dec 5, 2014 at 2:59 PM, David Cole dlrd...@aol.com wrote:
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
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.
gotta have the
latest update of VS for the WinStorePhone tests to work.
Does that match your expectations?
Thanks, and sorry for the temporary noise
David C.
On Tue, Nov 18, 2014 at 4:20 PM, David Cole dlrd...@aol.com wrote:
I just put VS 2013 Professional on it within the last two weeks
Putting continue, break or return inside of a macro definition is a
practice that should itself be discouraged...
(I know, people will probably still have cases of it, but it doesn't
seem like that's what any sane person would label a good practice, let
alone a best practice...)
On Tue, Nov 18,
over to the test script.
-Original Message-
From: David Cole [mailto:dlrd...@aol.com]
Sent: Friday, November 14, 2014 10:42
To: Gilles Khouzam
Cc: Brad King; cmake-developers@cmake.org
Subject: Re: [cmake-developers] Failing CMake WinStorePhone tests
I was hoping you'd say
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
Hi,
The VSWinStorePhone tests are failing on my dashboard submissions:
http://open.cdash.org/viewTest.php?onlyfailedbuildid=3570369
http://open.cdash.org/viewTest.php?onlyfailedbuildid=3570163
I just upgraded that machine to Windows 8.1 and Visual Studio 2013,
and these dashboards run in a VS
Cole
Cc: cmake-developers@cmake.org; Gilles Khouzam
Subject: Re: [cmake-developers] Failing CMake WinStorePhone tests
On 11/14/2014 11:27 AM, David Cole via cmake-developers wrote:
Should I expect these tests to pass using Ninja, or is that beyond the
scope of the WinStorePhone support
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.)
I just looked at the diff, not the surrounding code, so forgive the
question if it's obvious when inspecting the code.. but here's a
question about your change before we push it into RC 2:
Is objectSources guaranteed to contain the same set of objects as mapping?
If so, I wonder why the code
These are the earliest CDash results available for CMake:
http://open.cdash.org/index.php?project=CMakedate=2014-07-09
(they're discarded after 120 days...)
On Thu, Nov 6, 2014 at 5:27 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Am Donnerstag, 6. November 2014, 12:44:12 schrieb Brad King:
On
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
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
I would say yes, too.
On Tue, Oct 28, 2014 at 3:27 AM, Daniel Pfeifer dan...@pfeifer-mail.de
wrote:
2014-10-27 21:33 GMT+01:00 Ben Boeckel ben.boec...@kitware.com:
On Mon, Oct 27, 2014 at 11:59:09 -0600, Orion Poplawski wrote:
Trying to bring a bit more attention to this:
Fedora is
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
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.
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
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 is the main use case for locking files and directories from the
CMake language?
I feel slightly uncomfortable, without being able to put my finger on
exactly why, with the prospect of adding this to CMake...
Behavior when there's a lock that still exists (by bug/mistake) after
CMake is done
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
Consider using CDash instead. It was Dart's drop-in replacement...
and is actively maintained today.
www.cdash.org
On Tue, Oct 7, 2014 at 6:46 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
I thought it would be interesting to install my own local dart server
to learn how to use CTest as
How about IN_RANGE and/or IN_SET options?
Where IN_RANGE takes two version numbers (low and high) and does the
equivalent of:
if ( (NOT ver VERSION_LESS low) AND (ver VERSION_LESS high) )
Or possibly even IN_RANGES with multiple ranges...
And IN_SET takes a list of explicit version numbers
Is the result of RelativePath guaranteed to be a directory name, or is
it possibly a file name?
If a directory, then perhaps . makes sense and wouldn't negatively
impact anything (other than cosmetically) if changed. But if a file,
then . doesn't make as much sense. . to me implies it is 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
Maybe it shouldn't even be a CPack thing. Maybe it should be an
install time step so that all CPack generators will contains signed
binaries if codesign is used...
D
On Mon, Sep 29, 2014 at 9:55 AM, clin...@elemtech.com wrote:
It should not be an error
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
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
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
What is the problem that this feature is trying to solve?
It seems unnecessary to me as a first-class feature of CMake. I must
be missing something...
But if you do pursue something like this, it seems to me that
install(TARGETS ...) should install all files including the wrapper.
Is this only
I like the cmake_policy(SET CMP0053 NEW) solution, too. We should
make a concerted effort to encourage module maintainers to do this
before the 3.1 release for as many modules as possible.
D
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
The rule is (roughly): after the first release candidate for a given
release, no more new features for that particular release. Only
continuing work to complete new features in rc1 and fixing regressions
reported from previous versions should go in subsequent release
candidates. Possible
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
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
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
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 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
I would say there are no gold standard find modules.
The gold standard is a project config file, like Qt5 has.
From http://www.cmake.org/cmake/help/v3.0/manual/cmake-qt.7.html :
the Qt 5 libraries are found using Config-file Packages shipped with
Qt 5
Also, search this page for Config
In this case just the one. I'm not that ambitious as I'm just
volunteering my time to various FOSS projects and still have to
maintain a day job to pay the bills!
:-)
In that case, I would recommend just getting it into shape so that it
works best for you. (But then, that's the way we've
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 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
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 was also thinking about setting up an alternative testing
infrastructure parallel to RunCMake which runs cmake in script mode
rather than performing configuration/generation.
This already exists in a form in the Tests/CMakeTests/*TestScript*
tests.
An example:
...I would prefer to combine into something more compact.The other
infrastructure I don't think I have touched but optically it looks
very noisy.Having something that takes away repetitive tasks, more
compact and easier on the eye would be nice.
I agree. That would be nice. Feel free to
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:
Another approach might be to add STRING_EQUAL and STRING_MATCHES (or
similarly unambiguous names) operators that do not do the variable
lookup.
The documentation would start with:
if(string STRING_EQUAL string)
if(string STRING_MATCHES regex)
...i.e., not mentioning variable anywhere for these
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
Looks good to me. Why not merge it to 'next' for testing? Worst case,
you can also revert it and merge again...
D
--
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
Ok, how does it sound if we have a variable, such as
CMAKE_EXPORT_COMPILE_COMMANDS?
Let's say, CMAKE_EXPORT_TARGETS_INFORMATION.
I would prefer CMAKE_EXPORT_TARGETS_FILE, or some name that implies it
is a filename value, with the value of the variable being the name of
the file to generate.
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
The approach looks reasonable, but having it unconditionally spit out a
file in cmGlobalGenerator regardless of generator is probably not what
we want. Seems like it should be based on a variable, or be in a
specific generator, or somehow have a limited scope.
HTH,
David C.
--
Powered by
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
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
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
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...
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
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
--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
201 - 300 of 3692 matches
Mail list logo
