o
many posts various places saying *not* to use add_definitions for flags.
Unfortunately, I've never seen an explanation of why.
So, which should I trust: the reference documentation, or the several people
who say differently? If add_definitions is bad for flags, why is that?
Thank you,
rivileges, but I've read that's not true of hardlinks or
junction points.
If you have to support building on the FAT filesystem, none of that will work.
--
Todd Greer
Principal Scientist, Affinegy, Inc.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
parent
CMake is supposed to effect the child CMake. I think the intent is that they
are only related via the arguments to ExternalProject_Add (including their
default values).
I welcome all corrections to any misapprehensions I may have.
Thank you,
Todd Greer
Principal Scientist, Affineg
directory with source and build
artifacts if that will be helpful (or I can file a bug and attach them there).
Just let me know.
Thank you for looking into this,
Todd Greer
Principal Scientist, Affinegy, Inc.
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cm
the '-GXcode' isn't
being handled properly. Does CMake require a space there?
My ExternalProject_Add command looks like this:
ExternalProject_Add(
gtest
SOURCE_DIR ${googletest_dir}
CMAKE_ARGS -Dgtest_force_shared_crt=ON
INSTALL_COMMAND ""
LOG_DOWNLOAD ON
LOG_CONF
rence.html#boost_config.boost_macro_reference.macros_that_describe_c__11_features_not_supported
--
Todd Greer
Principal Scientist, Affinegy, Inc.
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Theodore Papadopoulo
Sent: Wednesday, February 20, 2013 4:16 AM
To: Benjami
From one brief use of ExternalProject, I came to the conclusion that it should
be used when it makes sense to let CMake handle downloading the project in
question, and to otherwise use add_subdirectory. Others with more
ExternalProject experience may have greater insight, though.
--
Todd Greer
2012 at 4:48 PM, Todd Greer wrote:
> I have several libraries in my build that are declared in the same
> CMakeLists.txt (by add_library). Unfortunately, the Visual Studio
> generator (2010, but I don't think it matters) puts
> "CMakeFiles\generate.stamp" in the output di
I have several libraries in my build that are declared in the same
CMakeLists.txt (by add_library). Unfortunately, the Visual Studio generator
(2010, but I don't think it matters) puts "CMakeFiles\generate.stamp" in the
output directory for that CMakeLists.txt. Unless I'm mistaken, when being bu
