As was previously announced, CMake is stopping mailing list usage, and
has transitioned to a Discourse forum (https://discourse.cmake.org).
While new posts to the mailing list are disabled, all previous
discussion will be archived so that the knowledge can be searched
going forward.
Hopefully I
I am happy to announce that CMake 3.17.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the
I am proud to announce the third CMake 3.17 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the more
We are pleased to announce that CMake 3.16.5 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.5 since 3.16.4
I am building libssh with cmake. I have two versions of OpenSSL on my
system and need libssh to use the later version of OpenSSL, which is in
/usr/local/ssl/lib. I need that rpath both before and after install, as
libssh should always use that version of OpenSSL. To do that I've been
pa
I am proud to announce the second CMake 3.17 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the more
Reminder the CMake Discourse forum ( https://discourse.cmake.org )
is the preferred location for CMake questions and discussions. The
current mailman-based mailing lists will be disabled in April 2020,
and their archives will remain available after that.
Reminder for those who prefer email over
I am proud to announce the first CMake 3.17 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the more
file
> OUTPUT
> object_file_for_source_file
> COMMAND not-thread-safe-compiler --build on_source.file
> COMMENT
> "Building Source object"
> )
>
> add_custom_target DEPENDS on OUTPUT from all custom command's, but in
> order to prevent paralle
We are pleased to announce that CMake 3.16.4 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.4 since 3.16.3
We are pleased to announce that CMake 3.15.7 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.7 since 3.15.6
We are pleased to announce that CMake 3.16.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.3 since 3.16.2
A reminder that CMake is transitioning to Discouse, and by the end of
March 2020 the mailing lists will be read-only, and the archives
will remain available after that.
The Discourse forum for the CMake community is:
https://discourse.cmake.org
Discourse offers users more control over their
We are pleased to announce that CMake 3.16.2 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.2 since 3.16.1
We are pleased to announce that CMake 3.15.6 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.6 since 3.15.5
On Thu, 2019-12-12 at 15:15 +0100, René J.V. Bertin wrote:
> Hi,
>
> If I understand correctly, configuring CMake for building means
> bootstrapping a basic version of itself which is then run on the
> included CMakeLists.txt file. That takes a lot of time
> (comparative
We are pleased to announce that CMake 3.16.1 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.1 since 3.16.0
I am happy to announce that CMake 3.16.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the
You should report this on the CMake issue tracker:
https://gitlab.kitware.com/cmake/cmake/issues/
On Sat, Nov 23, 2019 at 12:03 PM Martin Krošlák wrote:
>
> Hi,
>
> I have recently encountered what I believe might be a bug, where
> INTERFACE_LINK_OPTIONS are not carried over s
> tested. I found a smart answer on SO to link against object files
> and
> that works ok but it's messy and a lot of manual setup after cmake
> project generation, probably impossible to automate in cmake.
>
> The other quick way is to change the VS project output to
I am proud to announce the fourth CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more
A Discourse forum is now available for the CMake community:
https://discourse.cmake.org
Discourse offers users more control over their level of participation,
allowing them to subscribe or unsubscribe by category or individual topic.
Users may choose to participate by web forum, email, or both
, Nov 2, 2019 at 2:36 PM Mahmood Naderan via CMake
wrote:
>
> Hi,
>
> May I know what is wrong with the specifying a non-system gcc path?
>
>
> $ cmake .. -DCMAKE_C_COMPILER=/storage/users/mnaderan/tools/gcc-6.1.0/bin/gcc
> -DCMAKE_CXX_COMPILER=/storage/users/mnader
Hi,
May I know what is wrong with the specifying a non-system gcc path?
$ cmake .. -DCMAKE_C_COMPILER=/storage/users/mnaderan/tools/gcc-6.1.0/bin/gcc
-DCMAKE_CXX_COMPILER=/storage/users/mnaderan/tools/gcc-6.1.0/bin/g++
-- The C compiler identification is
Hi,
Is there a CMake variable to set the stack size of a target?
Upon searching the issues, I came across this one -
https://gitlab.kitware.com/cmake/cmake/issues/17572 . It says that there is a
CMake variable CMAKE_CXX_STACK_SIZE, but it isn’t clear whether
CMAKE_CXX_STACK_SIZE can be used
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
I am proud to announce the third CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more
We are pleased to announce that CMake 3.15.5 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.5 since 3.15.4
>you have a "case discrepancy" between:
>BOOST_INCLUDE_DIR
>and>Boost_LIBRARY_DIRS
Yes. Thank you
Boost_LIBRARY_DIRandBoost_INCLUDE_DIR
Are correct. The cmake is now fine.
Regards,
Mahmood
--
Powered by www.kitware.com
Please keep messages on-topic and check t
ost_LIBRARY_DIR".
Cheers,
Marcel Loose.
--
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:
Even with the latest 3.15.4, I get the same error
$ cmake --version
cmake version 3.15.4
CMake suite maintained and supported by Kitware (kitware.com/cmake).
$ cmake -DBoost_NO_SYSTEM_PATHS=ON
-DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/
-DBoost_LIBRARY_DIRS=/storage
Hi CMake Mailing List,
I am using the CHECK_CXX_COMPILER_FLAG directive in a CMake file to detect
whether the compiler uses the "-fsanitize=address" compiler flag. I'm using the
g++ 7.3.0 compiler which supports this flag but the CHECK_CXX_COMPILER_FLAG
directive incorrectly
Thank you. I tried this command:
cmake -DBoost_NO_SYSTEM_PATHS=ON
-DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/
-DBoost_LIBRARY_DIRS=/storage/users/mnaderan/boost_1_65_1/build/lib/
-DBoost_ADDITIONAL_VERSIONS=1.65.1 ..
The paths are correct as you can see below:
$ ls
Hi,
I have read https://cmake.org/cmake/help/v3.0/module/FindBoost.html which
states some variables for boost library. I want to know where should I set
these variables. For example, in the terminal, I have written
$ export Boost_NO_SYSTEM_PATHS=ON
However, after I run "cmake ..&qu
s.
This has the caveat that CMP0011 must be set to NEW for it to work
(which should be the case with any sane project - CMP0011 was
introduced in 2.6, the oldest version recognized by
cmake_minimum_required().)
Kyle
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake F
Thanks. I found it much easier to use the installer package (.sh file).
I wanted a new gcc for building cmake. since the system default is 4.8.5.
The installer package is available and installed that to my custom folder.
Regards,
Mahmood
On Sunday, October 20, 2019, 8:58:25 PM GMT+3:30
On Mon, 2019-10-21 at 10:23 +0100, David Aldrich wrote:
> I have a simple CMake project with subdirectories:
>
> cmake_minimum_required(VERSION 3.10)
> project(MyProject VERSION 1.0.0)
>
> set(CMAKE_VERBOSE_MAKEFILE ON CACHE BOOL "ON")
>
> add_subdirectory(s
early()
> endif()
>
> # 3. Everything went well
> cmake_policy(POP)
> This produces the following output
>
>
> CMake Error at CMakeLists.txt:27 (my_macro):
> cmake_policy POP without matching PUSH
>
> CMake Error in CMakeLists.txt:
> cmake_policy PUSH withou
I am proud to announce the second CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more
The easiest way is to specify the custom compiler via the CC and CXX
environment variables.
On Sat, Oct 19, 2019 at 2:19 PM Mahmood Naderan via CMake
wrote:
>
> OK and how about custom installation path of cmake?
>
>
> Regards,
> Mahmood
>
>
> On Saturday, October 19
OK and how about custom installation path of cmake?
Regards,
Mahmood
On Saturday, October 19, 2019, 4:44:28 PM GMT+3:30, 15 knots
wrote:
What worked for me, is to add 'ools/gcc-7.1.0/bin/' in front of the
PATh environment variable for the time cmake is invoked. E.g from
Hi
I would like to compile cmake source with a non default gcc version. That is, I
have built gcc in my home$ ls tools/gcc-7.1.0/bin/
c++ gcc-ar gcov-dumpx86_64-pc-linux-gnu-gcc
x86_64-pc-linux-gnu-gcc-ranlib
cpp gcc-nm gcov-toolx86_64-pc-linux
ad me misreading your
script. My advice is mainly based on this error:
CMake Error at build/patch_script.cmake:3 (string):
string sub-command REPLACE requires at least four arguments
Looking at this line:
string(REPLACE \"sys.prefix\" \"os.environ[\\\'SIRF_INSTALL_PATH\\\&#
It looks like you aren't passing the $testdata variable down to the script.
>From your message it looks like you need to add the following to your
PATCH_COMMAND:
-Dtestdata=${testdata}
You must explicitly pass $testdata (and any other variables defined in the
calling script) to patch_script.cmake
Hi Paul,
As another reference point, I verified that -DCMAKE_UNITY_BUILD=ON
works with the VTK-m ( https://gitlab.kitware.com/vtk/vtk-m ) project.
I only verified using a clean CMake 3.16 build directory.
On Thu, Oct 10, 2019 at 6:43 PM Paul Smith wrote:
>
> On Thu, 2019-10-10 at 14:57
--
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.org/cmake/help/support.html
On 10/10/19 6:53 PM, Paul Smith wrote:
> Is there an intent to address this before the 3.16 release?
>
> Or is this a known limitation, which may or may not be addressed in
> some future version of CMake?
>
> If the latter it should probably be added to the release notes and/
I am proud to announce the first CMake 3.16 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the more
That's the piece of the puzzle I was missing. Thank you!
Yes, I had deleted the cache because I thought that would force a complete
regeneration. I'm using a rather complicated system of ExternalProjects (LLVM),
so I figured it was the quickest way to essentially force cmake to start
If you want to do a clean rebuild you can do the following:
ninja clean or cmake --build --target clean
ninja or cmake --build -j N
On Wed, Oct 9, 2019 at 12:00 PM Nagurne, James wrote:
>
> That's the piece of the puzzle I was missing. Thank you!
>
> Yes, I had deleted th
The default generator and all other associated information ( '-D' ) is
kept in the CMakeCache.txt file in the root of the build directory.
The execution of `cmake -S -B ` will reload
this cache before doing anything else. Have you verified that your
build directory hasn't deleted
Hi all,
My question comes from a Ninja generator build system, and is specifically
about an internal rule generated by cmake.
What is the purpose of the RERUN_CMAKE rule generated by CMake with a Ninja
generator?
In the current repo, the only reference to this rule is in
ing about this,
unfortunately:
https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_LINK_EXECUTABLE.html
Is there, for example, a way to access arbitrary target properties?
Or do I need to hide my special parameters somewhere in the LINK_OPTIONS
property?
Regards,
Sebastian
--
Powered b
To avoid repetition, please view:
https://stackoverflow.com/questions/58253100/how-to-use-lld-with-cmake-on-windows
Sent with [ProtonMail](https://protonmail.com) Secure Email.--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
{}.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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
. Oktober 2019 12:56
To: Setzer Sebastian (CM-CI2/ECS2)
Cc: cmake@cmake.org
Subject: Re: [CMake] DEPENDS parameter of add_custom_target
On Mon, Oct 7, 2019 at 9:32 PM Setzer Sebastian (CM-CI2/ECS2) via CMake
<mailto:cmake@cmake.org> wrote:
Dear list,
The manual says:
https://cmake.o
Dear list,
The manual says:
https://cmake.org/cmake/help/latest/command/add_custom_target.html
Reference files and outputs of custom commands created with
add_custom_command() command calls in the same directory (CMakeLists.txt file).
They will be brought up to date when the target is built.
Use
Hello,
I’m experiencing an odd problem where no matter how I set CMP0093, it seems to
use the ‘NEW’ behaviour, breaking some other code relying on the OLD behaviour.
This is Cmake 3.15.4 from Homebrew, other people do report on other platforms
do report the policy working for them. Here’s my
To avoid repetition, please view:
https://stackoverflow.com/questions/58253100/how-to-use-lld-with-cmake-on-windows
Sent with [ProtonMail](https://protonmail.com) Secure Email.--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
That is, the "development" package still does
> not depend on the "runtime" package.
> So I try this:
> set(CPACK_COMPONENT_DEVELOPMENT_DEPENDS RUNTIME)
> in case capitalization is required. Now the "runtime" component seems
> to get packaged twice (
ww.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.org/cmake/help/support.html
CMake
On Thu, 2019-10-03 at 16:30 -0400, stefan wrote:
> Hi Kyle,
> thanks for the quick followup.
> On 2019-10-03 4:23 p.m., Kyle Edwards wrote:
> > Please take a look at cpack_add_component():
> > https://cmake.org/cmake/help/latest/module/CPackComponent.html
> I'm not su
On Thu, 2019-10-03 at 16:15 -0400, stefan wrote:
> I'm trying to generate (debian) packages for a project of mine using
> cmake. I need to generate multiple components ("runtime",
> "development", etc.). What is the expected way to have the
> "developmen
We are pleased to announce that CMake 3.15.4 is now available for download.
This release fixes a regression in EXCLUDE_FROM_ALL.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support
We are pleased to announce that CMake 3.14.7 is now available for download.
This release fixes a regression in EXCLUDE_FROM_ALL.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support
On Tue, 2019-09-24 at 23:41 +0300, Avraham Shukron wrote:
> Hi!
>
> I have a library which I want to distribute in both shared object and
> static library forms.
> Is there a modern way to do it without creating two completely
> separate library targets?
> Since I want to be
On 9/23/19 10:24 AM, Jakub Imriska wrote:
> Is there a way to retain the old behavior?
We thought the change was backward compatible with existing projects but
perhaps not.
I've opened an issue:
https://gitlab.kitware.com/cmake/cmake/issues/19753
Thanks,
-Brad
--
Powered by www.kit
file at the end of my 'myClass.cpp" file, then the moc file will
> be compiled there, otherwise CMake will take matters into its own
> hands and compile it anyway.
>
> Now suppose make my class into a static library. The static library
> now contains the object code generated
On Wed, 2019-09-11 at 17:33 -0400, Michael Jackson wrote:
> Already looked on google and at the CMake documentation but
> everything listed does not seem to work so here is the setup.
>
> I am using MKL and I have a home grown FindMKL since there isn’t an
> official one. Ins
On Wed, 2019-09-11 at 22:00 +0300, Avraham Shukron wrote:
>
>
> On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards m> wrote:
> > You can list them or not list them. CMake will recognize them as
> > header
> > files and ignore them (not attempt to compile them.) It&
On Wed, 2019-09-11 at 21:40 +0300, Avraham Shukron wrote:
> Hi!
>
> I'm pretty new to cmake and I came across a question which I could
> not find any information about in the official documentation or blog
> posts.
>
> When adding a target through add_library / add
to it?
>
> Isuru
Use a semicolon:
CMAKE_FLAGS "-DINCLUDE_DIRECTORIES=dir1;dir2"
Kyle
--
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. Fo
On Wed, 2019-09-04 at 14:12 -0400, fdk17 wrote:
> https://github.com/microsoft/vscode-cmake-tools/issues/752 states
> that it ran out of stack and the log shows what looks like to be
> involved with a recursive loop in some CMakeLists.txt. A call depth
> of 27491 seems a bit excessive
We are pleased to announce that CMake 3.15.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.3 since 3.15.2
ional arguments with cmake. Which make passing dynamic arguments
unreliable.
Am I correct? Is this a feature or a bug?
Regards,
[1] https://stackoverflow.com/questions/52480737/pass-empty-strings-in-cmake
[2] https://cmake.org/pipermail/cmake-developers/2015-July/025640.html
[3] https://cmak
ional arguments with cmake. Which make passing dynamic arguments
unreliable.
Am I correct? Is this a feature or a bug?
Regards,
[1] https://stackoverflow.com/questions/52480737/pass-empty-strings-in-cmake
[2] https://cmake.org/pipermail/cmake-developers/2015-July/025640.html
[3] https://cmak
On Thu, 2019-08-29 at 18:27 +0100, hex wrote:
> hello community,
>
> CMake builds a C project with gcc -o target_name. I have a compiler
> very similar to GCC and I am trying configure CMake C language for
> it.
>
> The compiler does not support the -o argument when linkin
tegrity"
Green Hills MULTI: -T not specified; defaulting to
"C:/ghs/comp_201255_RH850"
The C compiler identification is GHS
The CXX compiler identification is GHS
Check for working C compiler: C:/ghs/comp_201255_RH850/ccrh850.exe
Check for working C compiler: C:/ghs/comp_201255_RH8
Hi how do I configure cpack in cmake to execute a custom command in the install
directory.
I want to install windows service that is packaged within my installer and
extracted to specific install location.
Thanks in advance
Sent from Mail for Windows 10
--
Powered by www.kitware.com
Please
1-614-6246
http://science.gsfc.nasa.gov/sed/bio/matthew.thompson
From: CMake on behalf of "Deij-van Rijswijk, Menno"
Date: Wednesday, August 7, 2019 at 2:56 PM
To: "cmake@cmake.org"
Subject: [EXTERNAL] [CMake] Fortran support for ninja
Hello,
Today I was trying to use the Nin
atthew.thompson
From: CMake on behalf of "Deij-van Rijswijk, Menno"
Date: Wednesday, August 7, 2019 at 2:56 PM
To: "cmake@cmake.org"
Subject: [EXTERNAL] [CMake] Fortran support for ninja
Hello,
Today I was trying to use the Ninja generator for CMake on a project containi
> Is there a way for me to tell CMake what source files my command relies on so
> it knows when it needs to do a reconfiguration?
CMAKE_CONFIGURE_DEPENDS can do that.
https://cmake.org/cmake/help/latest/prop_dir/CMAKE_CONFIGURE_DEPENDS.html
--
Powered by www.kitware.com
Please keep me
would like this so that we can concatonate all of our Fortran source
files into a single file for interface checking (since there is only a
limited use of modules or explicit interfaces).
Thanks,
Chip
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http
HI Kyle,
Where are the -D and the -P switches of add_test documented?
Thanks for the suggestion.
On 6/20/2019 3:52 PM, Kyle Edwards wrote:
On Thu, 2019-06-20 at 15:45 -0400, Donald MacQueen [|] via CMake wrote:
I have a test where I start a program that I know will create some
output that I
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.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.
enario: Enabling compiler developer mode
Given a completed build
When I run CMake with arguments "-DCOMPILER_DEVELOPER=ON"
And I build
Then it shouldn't do anything
Scenario: Editing a compiler source file when in compiler developer mode
I'm using the Clang/LLMV APIs to build a code analysis tool that gives my users
some additional analysis of their C++ codes, above and beyond what the
compiler, proper, provides.
With a set(CMAKE_EXPORT_COMPILE_COMMANDS ON) in CMakeLists.txt, cmake emits a
"compilation data
All,
I am pleased to announce that we are now offering Ubuntu builds of the
CMake release candidates, in addition to the production releases. The
first available release candidate build is 3.15.0~rc1-0kitware2.
If you would like to receive release candidate builds, follow the
instructions at
On Wed, Jun 5, 2019 at 9:29 AM Bryan Christ wrote:
> Tom,
>
> I'll give that a try. Can that variable be changed after project() is
> called?
>
Yes, you should be able to change it at any point in your CMake script(s).
Remember that CMAKE__LINKER_FLAGS will effect all
echo first
sleep 1
echo second
sleep 1
echo third
$ cmake --version
cmake version 3.15.0-rc1
...
$ cmake .. -GNinja
$ ninja UseTerminal
...
first
second
third
```
While ninja is running I can see one line print at a time separated
by one second each.
Please try to provide a more complete standa
I think you want CMAKE_SHARED_LINKER_FLAGS:
https://cmake.org/cmake/help/latest/variable/CMAKE_SHARED_LINKER_FLAGS.html
You can also use target_link_libraries to pass linker flags:
https://cmake.org/cmake/help/latest/command/target_link_libraries.html
On Tue, Jun 4, 2019 at 1:12 PM Bryan
I am proud to announce the first CMake 3.15 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.15
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.15/release/3.15.html
Some of the more
and
> not only the part the is in the (), i need only the part from the ()
> - is there another command i can use for this ?
CMAKE_MATCH_1
Kyle
--
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
t; >
> > https://paste.debian.net/1086040/
> >
> > and i just try to traverse a list and include files whose part of
> > the
> > name are the list entries.
> >
> >
> > best regards!
> >
Please see the foreach() documentation:
https://cmake
uot;
> and i want the get the content of the found variables in the (), the
> command i used stored them if MATCH_XYZ but i can't exactly rember
> =(.
>
>
> best regards!
CMAKE_MATCH_
https://cmake.org/cmake/help/v3.14/variable/CMAKE_MATCH_n.html
Kyle
--
Powered by www
does not search recursively. See
the find_program() documentation for more details:
https://cmake.org/cmake/help/v3.14/command/find_program.html
Again, for GCC, I strongly recommend that you use a toolchain file,
rather than setting CMAKE_C_COMPILER from inside your project. CMake
does a bunch of che
PATHS "C:"
> )
> endif()
>
> message(STATUS "${_TOOL}")
>
> Result after executing: cmake -P mycmake.cmake
>
> -- On windows
> -- _TOOL-NOTFOUND
>
> Can anyone tell me what is wrong with the usage of "find_program" ?
find
Hi All,
This summer between July 22 - 25th Kitware is offering 7 free courses
over 3 days at our new headquarters in Albany NY. One of the free
courses we will be offering is a full day CMake course on Tuesday July
23rd. Hopefully some of you will be able to attend, and we can meet in
person
gt; Hi everyone,
>
> i'm relative new to cmake (a few weeks now) and i have the following
> problem:
>
>
> set(WITH_LIB_GLAD 1)
>
> IF(DEFINED ${WITH_LIB_GLAD}_INC_PATH)
>
> I try to check if the variable WITH_LIB_GLAD_INC_PATH can be found.
>
>
> best regards!
&g
b} is "WITH_LIB_GLAD" but allways return false =(
> if(_var STREQUAL ${lib})
Should be:
if(_var STREQUAL lib)
due to how if() expands variable references.
https://cmake.org/cmake/help/v3.14/command/if.html#variable-expansion
Kyle
--
Powered by www.kitware.com
Please kee
1 - 100 of 818 matches
Mail list logo
