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
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
The return code indicates a stack overflow. Let's hope it is not intended.
https://stackoverflow.com/questions/50562192/process-finished-with-exit-code-1073740791-0xc409-pycharm-error
On Thu, Aug 22, 2019 at 7:16 AM Nagy-Egri Máté Ferenc via
cmake-developers wrote:
>
> Hi!
>
>
>
> Someone
Before you login, it's just a "login" link. Once you've logged in, it
becomes a "My CDash" link.
On Sun, May 26, 2019 at 2:34 PM Alan W. Irwin
wrote:
>
> On 2019-05-26 11:07+1000 Craig Scott wrote:
>
> > Notifications for builds are controlled through CDash. You can adjust your
> > CDash
I would just like to point out that some modules (ExternalData,
ExternalProject, to name two specific examples) adopted the convention
to prefix all their provided function names with the module name and
an underscore: for example, ExternalProject_Add and
ExternalData_Expand_Arguments.
These
The code looks wrong like this, too:
You shouldn't strip the source directory from the path of the file
name unless the character after the source directory is "/" or "\\",
should you? If the thing you're trying to end up with is a path name
to the file under the source directory, then this is
I had a project where I had to do this in the main.cpp file to get it
to link with static Qt on Windows:
#ifdef _WIN32
#ifdef QT_STATIC
Q_IMPORT_PLUGIN(QWindowsIntegrationPlugin)
#endif
#endif
Those unresolved externals you posted look familiar... Does this fix it?
HTH,
I think your analysis is correct.
You could try doing a ctest_submit after each ctest_test call. Not
sure if you could get "correct" results with that technique. I run
some scripts that do something similar without subproject involved,
and it mostly works, but messes up the +/- tests passed and
to find the exact
one you already know you have...
On Tue, Aug 29, 2017 at 11:49 AM, Brad King <brad.k...@kitware.com> wrote:
> On 08/29/2017 11:33 AM, David Cole wrote:
>> That's correct:
>>
>> find modules do what they want, and most do not pay attent
to find the exact
one you already know you have...
On Tue, Aug 29, 2017 at 11:49 AM, Brad King <brad.k...@kitware.com> wrote:
> On 08/29/2017 11:33 AM, David Cole wrote:
>> That's correct:
>>
>> find modules do what they want, and most do not pay attent
ctory
>> ("installed") because I have other libraries that get installed in
>> that directory, each with their own directory to contain their
>> installation files. If find_package() is appending to
>> like it says it should, it should find each one of them witho
ctory
>> ("installed") because I have other libraries that get installed in
>> that directory, each with their own directory to contain their
>> installation files. If find_package() is appending to
>> like it says it should, it should find each one of them witho
t get installed in
> that directory, each with their own directory to contain their
> installation files. If find_package() is appending to
> like it says it should, it should find each one of them without
> switching the value of CMAKE_PREFIX_PATH.
>
> Am I misunderstanding som
t get installed in
> that directory, each with their own directory to contain their
> installation files. If find_package() is appending to
> like it says it should, it should find each one of them without
> switching the value of CMAKE_PREFIX_PATH.
>
> Am I misunderstanding som
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
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
This is great to see CMake continuing to evolve like this!
What's next, a web page CMake UI connected to cmake server instances
on multiple platforms? ;-)
On Wed, Aug 16, 2017 at 6:05 PM, Daniel Pfeifer wrote:
> On Wed, Aug 16, 2017 at 6:16 PM, Eric Wing
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
sts.txt:if(CMAKE_CONFIGURATION_TYPES)
On Wed, Aug 2, 2017 at 2:42 PM, Marcus D. Hanwell
<marcus.hanw...@kitware.com> wrote:
> On Wed, Aug 2, 2017 at 1:32 PM, David Cole <dlrd...@aol.com> wrote:
>> Very cool, Marcus. Thanks for the blog post.
>>
>> Florian, when you
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
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 <mailingli...@xgm.de> wrote:
> Hi,
>
> Am 01.08.2017 um 18:32 schrieb David Cole via CMake:
>> What source files include the h
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
Alan, you had said in your original post:
"Using find and xargs -0 grep I have looked in both 3.7.2 and 3.9.0
source code for any mention of CMAKE_Java_CREATE_SHARED_MODULE, and it
just does not exist."
Try searching for "_CREATE_SHARED_MODULE" instead... it's combined in code with
the name of
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.
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,
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,
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,
Is there a good reason why this error must be an error?
CMake Error at CMakeLists.txt:23 (add_library):
add_library cannot create ALIAS target "MyProj::gtest" because target
"OtherProj::googletest" is IMPORTED.
The line of code is:
add_library(MyProj::gtest ALIAS
ns those files will
> not get packaged when 'A_package' invokes `ant release` for the APK
> packaging.
>
> I hope that makes the issue a little clearer... sorry for the confusion.
>
> On Thu, May 18, 2017 at 1:22 PM, David Cole <dlrd...@aol.com> wrote:
>> Seems to m
arly, but I wanted to hash out the details because maybe there is a
> better approach. I'm willing to start from scratch on this if it
> improves the design of the targets.
>
> Thanks again!!
>
>
> On Thu, May 18, 2017 at 10:51 AM, David Cole <dlrd...@aol.com> wrote:
owever, if C was set
> up using `ALL`, will it build C when I build B? So the expected build
> order in this case would be:
>
> 1. A
> 2. B
> 3. C
>
> Thanks in advance.
>
> On Wed, May 17, 2017 at 4:26 PM, David Cole <dlrd...@aol.com> wrote:
>> The way I kn
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
>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,
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
t.
D
On Fri, Mar 24, 2017 at 3:11 PM, Eric Noulard <eric.noul...@gmail.com> wrote:
> Hi David,
> Thank you for you for checking the code. Would you think adding such a
> command line option would be acceptable upstream?
>
> Le 24 mars 2017 18:43, "David Cole" <
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
Have you looked into
https://github.com/Kitware/CMake/blob/master/Modules/CMakeDetermineCSharpCompiler.cmake
?
Send steps to reproduce the problem you're seeing... Maybe somebody
else here has encountered the same thing and worked through it
already.
HTH,
David C.
On Wed, Mar 22, 2017 at
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
>
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
ORY and
> disable the internet to reproduce:
>
> 1) git clone https://github.com/ericniebler/range-v3.git LOCAL_CLONE_DIR
> 2) Add ExternalProject_Add(range-v3 GIT_REPOSITORY LOCAL_CLONE_DIR) to a
> project
> 3) Disable the internet
> 4) Attempt to build
>
> ** Watch it hang, and
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
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
"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
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
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
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:
>
> SeverityCode
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
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
Looks like you could also use a list of paths if you express them in
"file://..." form. Local files can also be expressed as URLs.
David C.
On Wed, Jul 13, 2016 at 4:18 AM, Schmertmann, Lars
wrote:
> Hello there,
>
> I try to continue the work from André.
>
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
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
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
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
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 :
>
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
Brad's point with "/" or null terminator was that the directory name
**must** be the directory itself, or a sub-directory of the one in
question.
i.e.
if it's "my/src"
then it should either be exactly "my/src" or "my/src/someSubDir" , not
"my/srcSiblingDir"
On Fri, Mar 18, 2016 at 11:52 AM,
t;
>> CMake Error at C:/Program Files
>> (x86)/CMake/share/cmake-3.4/Modules/GetPrerequisites.cmake:798 (message):
>> 106>C:/Program Files (x86)/Microsoft Visual Studio
>> 12.0/VC/bin/dumpbin.exe
>> 106>failed: 1181
>>
>> I'm digging
>
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
Seems to me like C# support should work just fine with other generators: ninja,
nmake, and UNIX Makefiles included. Especially with mono on Linux/Mac.
David
> On Mar 7, 2016, at 2:12 PM, Brad King wrote:
>
>> On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP
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
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
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:
>
>
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
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
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
I agree with Brad, the --timeout command line parameter should only
set/override the variable CTEST_TEST_TIMEOUT. The behavior w.r.t. test
TIMEOUT properties should be left as is for this change.
A **new** --timeout-scale with well defined / documented interactions
with the global variable and
e with good projects.
David
> On Dec 17, 2015, at 2:42 PM, Ben Boeckel <ben.boec...@kitware.com> wrote:
>
>> On Thu, Dec 17, 2015 at 13:54:08 -0500, David Cole wrote:
>> I agree with Brad, the --timeout command line parameter should only
>> set/override the variable CTEST
d -D cmd line params since 3.0 or so.
David
> On Dec 17, 2015, at 6:38 PM, Alan W. Irwin <ir...@beluga.phys.uvic.ca> wrote:
>
>> On 2015-12-17 13:54-0500 David Cole wrote:
>>
>> I agree with Brad, the --timeout command line parameter should only
>> set/over
Thanks, Ben. That was gonna be my 2 cents, too:
If I set a test property to have a 1, 5 or 10 second timeout, then I
want the test to timeout if it takes any longer than that. I do this
on tests which must execute quickly even in a loaded CPU scenario. I
would not want the global timeout to take
ng CXX compile features - done
> -- Found PythonInterp: C:/Python27/python.exe (found version "2.7.10")
> -- Configuring done
> -- Generating done
>
>
> Yves
>
> On Thu, Dec 10, 2015 at 12:58 PM, David Cole <dlrd...@aol.com> wrote:
>
>> Out of curi
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:
$ 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",
Yes, that looks like it should work. I'll pull your branch and give it a
try sometime in the coming week.
Thanks,
David
On Friday, December 4, 2015, Daniel Pfeifer <dan...@pfeifer-mail.de> wrote:
> On Fri, Dec 4, 2015 at 11:32 PM, David Cole <dlrd...@aol.com
> <javascript:;&
With Visual Studio, you definitely **need** separate pch for each CONFIG.
Every pch is going to include headers which have Debug/Release differences
in them, and it is not safe to mix and match compiler output from separate
configs together.
D
On Friday, December 4, 2015, Daniel Pfeifer
egarding these two questions:
>>> - Do we want to support different pch per CONFIG? I think no, but I
>>> might be wrong.
>>> - Do we want to support different pch per LANGUAGE? I first thought
>>> yes, but I am no longer certain about that.
>
> On Fri, De
dio tester for you.
D
On Fri, Dec 4, 2015 at 5:28 PM, Daniel Pfeifer <dan...@pfeifer-mail.de> wrote:
> On Fri, Dec 4, 2015 at 9:19 PM, David Cole <dlrd...@aol.com> wrote:
>> Right, I was talking about the pch-binary.
>>
>> Why would CMake even need to generate a h
What OS? What version of CMake? What version of VTK? Did you download
CMake, and if so, from where? Or did you build CMake yourself?
On Tue, Nov 24, 2015 at 7:27 AM, Constantinus Spanakis
wrote:
> Hello, i tried to configure VTK using Cmake, but every time it stucks
>
> ```
> Adding the output files to the SOURCES makes the target do what's its
> supposed to do.
>
> Cheers,
> Nico
>
> On Sun, Nov 22, 2015 at 11:59 PM David Cole <dlrd...@aol.com
> <javascript:_e(%7B%7D,'cvml','dlrd...@aol.com');>> wrote:
>
>> You don't.
rstanding of me then. Thanks!
> How do I make a test depend on a target then?
>
> Cheers,
> Nico
>
>
> On Sun, Nov 22, 2015 at 8:58 PM David Cole <dlrd...@aol.com
> <javascript:_e(%7B%7D,'cvml','dlrd...@aol.com');>> wrote:
>
>> The DEPENDS property of a tes
other targets (e.g., `
> testFetchData`). (Full CMakeLists.txt at [1].) Explicitly calling `make
> convert` works alright.
>
> Any idea why that might be?
>
> Cheers,
> Nico
>
> [1] http://chunk.io/f/729beeab41fb4a7385ceb98b31a2ea0a
>
> On Sun, Nov 22, 2015 at
doesn't do the trick: The target `convert` isn't executed before `ctest`.
>
> Any hints?
>
> Cheers,
> Nico
>
>
> On Sun, Nov 22, 2015 at 3:18 AM David Cole <dlrd...@aol.com
> <javascript:_e(%7B%7D,'cvml','dlrd...@aol.com');>> wrote:
>
>> Did you try
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
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
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
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
s
the one triggering this warning slipping through as unignored?
HTH,
D
On Thu, Nov 5, 2015 at 10:01 AM, Rashad M <mohammedrasha...@gmail.com> wrote:
> yes.
>
> On Thu, Nov 5, 2015 at 1:46 PM, David Cole <dlrd...@aol.com> wrote:
>>
>> Does your ctest -S script call ctest_r
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 <dlrd...@aol.com> wrote:
> Because you're giving DEPENDS as a target name, this is only an ordering
> dependency, stating that
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
A simple source tree grep for "HKEY" (or even just "HK") will point you to
all the places CMake has registry key references in its source code...
On Tue, Oct 27, 2015 at 10:38 AM, Johannes Asal
wrote:
> If it was actually using registry entries only for locating the VS
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)
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
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
Unfortunately, "pushd" is an inappropriate command to use when the
argument is quoted. It works just fine with "/" characters if the
argument is quoted...
For example:
C:\Users\davidcole>pushd C:\Windows\System32
C:\Windows\System32>pushd C:/dev
The syntax of the command is
the list of all available CMake targets, which
may be different than what the project had set into the property.
Thanks for any feedback,
David C.
On Mon, Jul 20, 2015 at 9:30 AM, Brad King <brad.k...@kitware.com> wrote:
> On 07/17/2015 06:05 PM, David Cole via cmake-developers wrote:
>
Honestly, KWSys has always seemed like a boost-avoidance mechanism
from an outsider's perspective. Perhaps it should be replaced with
boost equivalents in projects that need to be packaged for Fedora.
I assume all the boost libraries are already packaged/available.
Fuel for the fire, ;-)
D
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
with globally making this change to the existing tokens is
that there could be some external tool/program that is EXPECTING to get CMake
paths, not native paths. Who knows? I am guessing that is what David Cole
was concerned about.
Maybe the right answer is to introduce some NEW tokens while leaving
But some existing replacements require forward slashes, we can't just to
native path everything blindly. I think you will have to special case the
bits which do need native paths.
On Wednesday, August 19, 2015, Kislinskiy, Stefan
s.kislins...@dkfz-heidelberg.de wrote:
Hi,
I would like to
1 - 100 of 3692 matches
Mail list logo