On Mon, Apr 8, 2019 at 2:07 AM Cook, Steven (G&I)
wrote:
> Hi Nils,
>
>
>
> > Been a while since I looked at this but it still seems to work for me
> in 3.14.0.
>
> > Corresponding elements are generated in files.wxs:
>
>
>
> Can you please tell me
this but it still seems to work for me in
3.14.0.
Corresponding elements are generated in files.wxs:
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
also
work when users directly manipulated PDB specific compiler flags.
Nils
--
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 of
cesses are
reading/writing the same test.error file in parallel?
Haven't looked closer than that. You probably know better where to look
from there.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware off
;d want is:
https://cmake.org/cmake/help/latest/variable/CMAKE_FIND_ROOT_PATH.html
Nils
--
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
irectories-and-usage-requirements
Specifically the paragraph close to the end starting with "When the
INTERFACE_INCLUDE_DIRECTORIES of an imported target...".
Basically include directories inherited from imported targets are
implicitly "SYSTEM" by default.
Nils
--
Powered
intended? And why is it intended?
I work with cmake 3.9.1.
Thank you,
Nils
--
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
LIBRARY_TARGET_PREFIX} expands empty
add_custom_command() will receive an argument which it will escape /
quote as required by the build system.
Nils
--
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 ser
e base for examples on
how to use the libraries in their own code where consistency might be
beneficial.
It might also help (slightly) if you ever decided to split off parts of
your project into new projects (which then would become consumers of the
exported targets).
Nils
--
Powered by www.k
When the library target has a namespace CMake will require the given
name to be a target and will fail during generation if the target is not
actually available.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FA
ributed compilation via icecc
(icecream) [1] or distcc be an option?
Should work with both the Makefile and Ninja generators (replace compilers
with icecc/distcc compiler wrappers).
Nils
[1] https://github.com/icecc/icecream
--
Powered by www.kitware.com
Please keep messages on-topic and
n states [1]:
"Unlike the above |NAME| signature no transformation is performed
on the command-line to support target names or generator expressions."
Use the new signature instead e.g.:
add_test(NAME RunTests COMMAND MyTest)
Nils
[1] https://cmake.org/cmake/help/latest/comm
: /tmp/cmaketest
>
> Would you have expected "one;two" rather than "onetwo"?
>
When unquoted each list items is turned into a distinct argument for the
message() invocation.
message() concatenates its arguments hence "onetwo".
To preserve the semicolon in th
uild system will
know if something relevant has changed or not.
Nils
--
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 offeri
On 13.09.2017 14:31, Alain Miniussi wrote:
On 13/09/2017 12:49, Nils Gladitz wrote:
[...]
Do you have a minimal reproducible example for that behaviour?
e.g. given:
cmake_minimum_required(VERSION 2.8.0)
project(Foo NONE)
file(WRITE foo/CMakeLists.txt "add_execu
On 13.09.2017 12:22, Alain Miniussi wrote:
On 13/09/2017 11:16, Nils Gladitz wrote:
On 13.09.2017 10:52, Alain Miniussi wrote:
Hi,
Is there a way, when printing CMake error, to get the exact location
of the CMakeLists.txt ?
For example, right now, when I have:
CMake Error at
one has
add_executable at line 14.
CMake includes the (relative to the root source directory) path for me e.g.:
CMake Error at Source/CMakeLists.txt:4 (add_executable):
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
MATCHES ".*test")
Does cmake always search for a subexpression? Is there some way to
prevent this behaivor?
The regex syntax is documented here:
https://cmake.org/cmake/help/latest/command/string.html#regex-specification
if ("This is a test" MATCHES "^test")
CPack generator and compiler specific while the competing
https://cmake.org/cmake/help/latest/module/InstallRequiredSystemLibraries.html
is both generator and compiler agnostic.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/W
).
Also note if the C compiler has already been configured for a build tree
it can not simply be changed.
Which is also why the CC environment variable has no effect on build
trees where the C compiler is already configured.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and
THON_EXECUTABLE}" ${testfile})
It should enable generator expression processing in test properties.
Nils
--
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
On 17.07.2017 17:13, Deniz Bahadir wrote:
Am 17.07.2017 um 16:47 schrieb Nils Gladitz:
On 7/17/2017 3:52 PM, Deniz Bahadir wrote:
This works just fine. However, now I want to add an additional
build-step after creation of the object-files and before linking the
shared library. (In
IMHO, the most comfortable (and syntactically cleanest) way would be
my first attempt. But that is probably more a feature-request than a
simple question.
FWIW this was implemented in the upcoming 3.9:
https://cmake.org/cmake/help/latest/module/CPackIFW.html#command:cpack_ifw_configure_compo
IR}/tmp-pcode-matlab/knitromatlab_mip.p
COMMAND ${Matlab_MAIN_PROGRAM} -nodisplay -nodesktop -nosplash -r
"run('${CMAKE_BINARY_DIR}/generate_pcode.m');"
VERBATIM
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
COMMENT "Generating PCode")
Note the removal of all escape s
e should
work (works for me).
Nils
--
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:
Assuming you've installed sphinx and enabled e.g. SPHINX_HTML
(-DSPHINX_HTML=ON) you could try a verbose build of the "documentation"
target to see how a sphinx-build invocation looks like.
To change the builder modify the argument after the -b option (e.g.
replace "html"
N_DEBUG or LOCATION_RELEASE).
Nils
--
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: http://cmake
ren't populating its
IMPORTED_LOCATION [1] (or IMPORTED_LOCATION_ [2]) target property.
Without it CMake does not know what on disk library file to link to.
You can set target properties with set_property() or
set_target_properties().
Nils
[1] https://cmake.org/cmake/help/latest/prop_tgt/
ptions(), COMPILE_OPTIONS) and some expect strings
with whitespace separated arguments (e.g. CMAKE_C_FLAGS, COMPILE_FLAGS).
Presumably you are feeding the list to something that expects the latter.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
On 12.04.2017 17:48, Olumide wrote:
Thanks Nils.
BTW, shouldn't that be
ContinuumTransfunctioner$<$:_d>
Transmogrifier$<$:_d>
Ah right given your specific case, yes.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
htt
rget exports
and package configuration files:
https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html#creating-packages
Nils
--
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
Ubuntu 16.10 Docker container
and it worked there as-is.
Nils
--
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
On 03/31/2017 11:54 AM, Alan W. Irwin wrote:
Hi Nils:
And use of ExternalProject_Add, etc. In other words, this is a pretty
crippling restriction for users with Linux distributions (such as the
quite recent Ubuntu 2016.10 of the original poster) that do not yet
give access to libssl version
; support in curl which
would mean no "https://"; support in e.g. file(DOWNLOAD) and CTest
submissions.
Nils
--
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 C
g. "cmake ... -DCMAKE_USE_OPENSSL=false" or
"bootstrap ... -- -DCMAKE_USE_OPENSSL=false".
To point CMake at a custom OpenSSL installation instead setting the
CMAKE_PREFIX_PATH environment to the installation should work.
Nils
--
Powered by www.kitware.com
Please keep message
ect / accept those version suffixes.
Beyond that I can't think of anything other than debugging into
cmVSSetupHelper.cxx.
Nils
--
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
On 03/28/2017 03:17 PM, HarpyWar wrote:
Nils Gladitz, the command, which you proposed, return nothing, even on
a machine where a compiler found:
vswhere -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64
-requires Microsoft.VisualStudio.Component.Windows10SDK
For me it lists my
Microsoft.VisualStudio.Component.Windows10SDK
I think those are the default components CMake might expect when looking
for compatible installations.
Nils
--
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
/experience about using VS Code with CMake on Linux
would be great.
Did you see
https://marketplace.visualstudio.com/items?itemName=vector-of-bool.cmake-tools
?
Might have more potential with the noted CMake Server support than CMake
generated IDE files.
Nils
--
Powered by www.kitware.com
g ones e.g. "L1", "L2", "L1-L2".
I was pondering trying to implement test filtering based on the
condition evaluator CMake uses for if()/while() at some point
(cmConditionEvaluator.cxx).
e.g. --run-tests-if "L1 IN_LIST TEST_LABELS AND L2 IN_LIST TEST_LABELS"
doc/gflags-2.1.1/AUTHORS.txt
/usr/share/doc/gflags-2.1.1/COPYING.txt
/usr/share/doc/gflags-2.1.1/ChangeLog.txt
/usr/share/doc/gflags-2.1.1/README.txt
Did you also install the corresponding development package e.g.
"gflags-devel"?
Nils
--
Powered by www.kitware.com
Please keep message
or since the
backslash starts an escape sequence [1].
Nils
[1]
https://cmake.org/cmake/help/latest/manual/cmake-language.7.html#escape-sequences
--
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
Ninja generator
currently but either way the users mailing list might not be the best
place to reach the developers.
The issue tracker is available here:
https://gitlab.kitware.com/cmake/cmake/issues
The developers mailing list here:
https://cmake.org/mailman/listinfo/cmake-developers
Nils
re your install() commands?
Everything installed by "make install" should also land in the package
assuming what ever install logic you used honors the install time
CMAKE_INSTALL_PREFIX as set up by CPack.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMak
.
You might want to report the issue here:
https://gitlab.kitware.com/cmake/cmake/issues
and/or discuss the fix on the developers mailing list:
https://cmake.org/mailman/listinfo/cmake-developers
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at
by the existing policy.
Nils
--
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: http://cmake
ion >= 3.0 will issue a warning (when the required version
is < 3.0) or an error (when the required version is >= 3.0) by default:
https://cmake.org/cmake/help/v3.8/policy/CMP0037.html
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
h
uot;)
Now you've got both a regular and cache variable named X.
When expanded the regular variable takes precedence.
Is this OK? Is this documented anywhere?
https://cmake.org/cmake/help/v3.7/manual/cmake-language.7.html#variables
Nils
--
Powered by www.kitware.com
Please keep message
On 01/30/2017 02:26 PM, Dave Flogeras wrote:
On Sun, Jan 29, 2017 at 9:53 AM, Nils Gladitz <mailto:nilsglad...@gmail.com>> wrote:
FWIW I don't think -j does anything when you build the
NightlyBuild target given that that make invocation is not the one
directly perform
hidden by default.
Did you check the "Advanced" option in cmake-gui?
Nils
--
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
informati
ly command being run by the NightlyBuild target would be "ctest -D
NightlyBuild" (nothing to parallelize when there is only one command).
CTest would spawn another make process for the build.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
h
elaborate?
Any ideas, or how can I get more info on the failure ?
ctest -V or ctest --output-on-failure might help.
What type of failure does CTest indicate?
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FA
AUTOMOC specific but I think
(like the name implies) that it probably applies to all the AUTOGEN
variants.
Nils
--
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
Try add_library( Foo SHARED foo.c foo.h foo.md).
From what I remember the target properties in this case only apply to
sources that are associated with the target.
Unrelated but cmake_minimum_required() should come before project().
Nils
--
Powered by www.kitware.com
Please keep messages on
it is currently implemented).
e.g. if "abc" has custom commands that generate header files that "foo"
also depends on this will make sure they are created/updated before
"foo" makes use of them.
And more obviously "abc"'s library output is created/u
Well you could have excluded the case when I brought it up initially
preferably before asking for code.
I don't have any unmaintained public projects in mind that I could link to.
But then again as I said before the code itself is entirely irrelevant;
what counts is the context.
Nils
sts/RunCMake/CMP0054/CMP0054-NEW.cmake;h=23a912476024ba09fcf741e04f999b64a6e91450;hb=refs/heads/master
Again the code itself is irrelevant here; what matters is the context.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wik
to |OLD|, except to silence warnings
in an otherwise frozen or stable codebase, or temporarily as part of a
larger migration path."
Beyond that valid use would be e.g. cmake's own testsuite which needs to
be able to toggle individual policies to verify their behaviour.
Nils
--
Powe
On 09.11.2016 12:04, Ruslan Baratov wrote:
On 09-Nov-16 16:22, Nils Gladitz wrote:
On 09.11.2016 04:29, Ruslan Baratov wrote:
On 08-Nov-16 23:33, Nils Gladitz wrote:
On 11/08/2016 04:17 PM, Ruslan Baratov wrote:
Except it's exactly opposite :) `cmake_minimum_required` is about new
fea
On 09.11.2016 03:47, Ruslan Baratov wrote:
On 09-Nov-16 06:01, Nils Gladitz wrote:
I think the git tag creation dates should roughly equate release dates:
https://cmake.org/gitweb?p=cmake.git;a=tags
What about the future releases? There was a page
https://cmake.org/Bug/changelog_page.php
On 09.11.2016 04:29, Ruslan Baratov wrote:
On 08-Nov-16 23:33, Nils Gladitz wrote:
On 11/08/2016 04:17 PM, Ruslan Baratov wrote:
Except it's exactly opposite :) `cmake_minimum_required` is about new
features/commands, and policies is about behavior.
I don't agree and you can no
On 08.11.2016 20:26, Albrecht Schlosser wrote:
On 08.11.2016 15:22 Nils Gladitz wrote:
Strictly speaking cmake_minimum_required(VERSION) is not about command
availability but rather about behavior (cmake policies).
[...]
I'd start by requesting the highest possible version I could ju
On 11/08/2016 04:17 PM, Ruslan Baratov wrote:
On 08-Nov-16 22:22, Nils Gladitz wrote:
Strictly speaking cmake_minimum_required(VERSION) is not about command
availability but rather about behavior (cmake policies).
Except it's exactly opposite :) `cmake_minimum_required` is about new
fea
available / justifiable.
Nils
--
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: http:/
x27;t think this needs change.
You don't have to browse all versions of the documentation ... you only
have to work with the documentation that matches the version you
declared in cmake_minimum_required().
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
invoking cpack (the "PACKAGE" target that cmake generates does this
by default):
e.g. cpack -C Release -G WIX
The install properties are only generated for the known configurations.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www
e-wix-testsuite/blob/d01013e2066e68088b4f56a8ab7750eb3cea7089/property_start_menu_shortcuts/CMakeLists.txt
This still works for me using CMake 3.7.0-rc2.
CMake 3.7.0-rc2's own windows installer uses the same feature for the
start menu shortcut to the documentation which also seems to work for
remove existing elements and can not be used
to modify the attributes of existing elements.
Nils
[1]
https://msdn.microsoft.com/en-us/library/windows/desktop/aa372064(v=vs.85).aspx
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org
I need to take to make this work on
Windows?
mylib.lib is the import library [1] for your DLL.
The linker is (probably) not creating it because you aren't exporting
any symbols [2].
Nils
[1] https://en.wikipedia.org/wiki/Dynamic-link_library#Import_libraries
[2] https://msdn.microso
(MSVC)
set (HAVE_GL_GL_H 1)
endif (MSVC)
Is this what you suggest?
I suppose I'd go with if(WIN32).
Nils
--
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
On 08/22/2016 01:30 PM, Albrecht Schlosser wrote:
On 22.08.2016 12:54 Nils Gladitz wrote:
On 08/22/2016 12:18 PM, Albrecht Schlosser wrote:
On 22.08.2016 10:33 Nils Gladitz wrote:
The visual studio command line environments should have no effect when
using the visual studio generators
On 08/22/2016 12:18 PM, Albrecht Schlosser wrote:
On 22.08.2016 10:33 Nils Gladitz wrote:
The visual studio command line environments should have no effect when
using the visual studio generators.
Are you sure? Or what does "should" mean here? ;-)
Yes. The Visual Studio gene
be relevant when you use one of the command line
generators (e.g. makefiles or ninja).
Nils
--
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
tudio chooses and CMake just records that choice in
CMAKE__COMPILER.
Nils
--
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
round) the ambiguities that the policy warnings point to.
Nils
--
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, pl
/cmake-developer.7.html#find-modules
Nils
--
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
P0063 POLICY_VALUE_AFTER)
message("[${POLICY_VALUE_BEFORE}] [${POLICY_VALUE_AFTER}]")
file(WRITE foo.cpp "int main() {}")
set(CMAKE_CXX_VISIBILITY_PRESET hidden)
add_executable(foo foo.cpp)
Expectedly outputs for me:
[NEW] []
(plus the policy warning since CMP0063
previous cmake_policy(SET)
calls will have any effect.
Nils
--
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
inimum_required(VERSION) call? (e.g. is there more than one?)
Nils
--
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 offerin
cies based on the requested version.
Otherwise did you set the policy before creating your targets and in a
scope that is parent to all targets involved?
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitw
directories "CMake
Rules", "Object Files" and "Ressources" was. Beside the obvious expectation of their
meaning, they are still empty and I am not able to get them filled.
Thank you,
Nils
Date: Fri, 22 Apr 2016 20:33:47 +0200
From: Martin Weber
To:cmake@cmake.org
Subjec
try_compile() tests that cmake runs will correctly
determine that you are building 32-bit and find_library() will use the
correct paths.
Make sure you start with a fresh build directory.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www
I am curious as to what kind of use case results in having to require
cross-version information as provided by the compatibility matrix "a lot".
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
of these virtual
directories?
Thank you,
Nils
Am 20.04.2016 um 22:14 schrieb Alexander Neundorf:
On Monday, April 18, 2016 16:57:52 Nils Rathmann wrote:
Hi,
when I setup with the Eclipse CDT4 generator, as described here:
https://cmake.org/Wiki/Eclipse_CDT4_Generator4
my [Targets] folde
build next to the
source directory.
Thank you,
Nils
--
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
.
try:
message("${lib_dirs}")
Note the quotes.
Nils
--
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 offeri
.git;a=commit;h=f799ffb5cb895855ac2aba54765622b81db5be38
Which is in CMake since ~3.4.0.
The change is related to this issue:
https://cmake.org/Bug/view.php?id=15705
Nils
--
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 v
es compiler and platform
information that is not available in ctest scripts (e.g. boost library
file names can be mangled differently depending on which
compilers/versions are used and can be located differently depending on
bitness).
Nils
--
Powered by www.kitware.com
Please keep messages on-
execute_process() documentation it runs
the commands in parallel by design so that each process's output can be
fed to the next process's input.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offe
ed the old COMPILE_FLAGS property (which was
plain string based).
For LINK_FLAGS the same thing was supposed to happen at some point but
the topic working on this seems to have stalled.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
s this intentional or is this a bug?
LINK_FLAGS is not a list property; flags have to be whitespace separated.
You can use APPEND_STRING instead of APPEND for this.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
hes
are probably welcome.
Nils
--
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: ht
/v3.4/manual/cmake-developer.7.html#find-modules
Nils
--
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:
this behaviour?
This is due to how you call message() which concatenates its arguments.
Instead try e.g.
message(" -> All arguments: ${ARGV}")
Which should output " -> All arguments: 1;2;3" (CMake's internal list
separator is semicolon).
Nils
--
Powere
in [1]).
Incidentally using explicit source file listings would work around this
issue as well.
Nils
[1] https://cmake.org/cmake/help/v3.4/command/file.html
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
ou would therefor
have to put them into a common parent directory (distinct from the other
targets) and give that parent directory's CMakeLists.txt its own
project(Myproject) call.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://ww
is supported. Am I wrong? Do I have to manually set the
INTERFACE_LINK_LIBRARIES of B?
Yes you have to set INTERFACE_LINK_LIBRARIES.
add_dependencies() is for order (not link) dependencies.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
y toolsets)
link_libraries() [1] might have the smallest impact if you do end up
having to modify the project.
Nils
[1] https://cmake.org/cmake/help/v3.4/command/link_libraries.html
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
deBlocks - Ninja" would be an option?
ninja builds parallel by default.
Nils
--
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
#x27;t checked) and more that users might just
expect them to be set (which does not provide a diagnostic).
Personally I would not object to either approach as long as there are
actual use cases.
Without use cases such changes would be by definition useless.
Nils
--
Powered by www.kitware.com
1 - 100 of 460 matches
Mail list logo
