Re: [CMake] Link options not transitive

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 static libraries. >

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-408-gae2c2f1f1b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ae2c2f1f1b5c81ea90579b605a61e9ae96b3178b (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-407-gadc50529ac

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via adc50529ac163889c0353756706a7ffddb4ed957 (commit) from

Re: [CMake] Testing an exe with gtest - possible?

Thanks, this pointed me in the right direction. I ended up moving main() to it's own file so nothing depends on it, using a static add_library (project sources minus the main.cpp) and depend on that target from gtest exe project. Works like a charm. I missed the discourse announcement, I'll

[CMake] Link options not transitive

Hi, I have recently encountered what I believe might be a bug, where INTERFACE_LINK_OPTIONS are not carried over static libraries. Following is the simplest CMakeLists.txt that demonstrates the problem: cmake_minimum_required(VERSION 3.16) project(LinkOptionsNotTransitive) add_library(A SHARED

Re: [CMake] Missing dll on program startup - a way automate it?

Thanks, this is exactly what I need. Unfortunately constructing the path expansion involves some gymnastics. If Find* exposes a list of directories it's just a simple list join (-> boost) but if it does not it is more involved.. list(JOIN Boost_LIBRARY_DIRS ";" BOOST_PATH) set(ZLIB_PATH "")

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-406-gd8571ccb9c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via d8571ccb9c4c7e6eca33779c083bd501b1782030 (commit) from

[CMake] Executing custom command behavior.

Hi, what exactly is the difference between the following both variants of adding an executable and sources to a project? I probably should add that for both versions the build happens via a custom command added via add_custom_command( TARGET ${cmake_target} POST_BUILD ... ) Hence I set

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-405-g07226324eb

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 07226324ebd179a22cf581f31be07b71ab160ce6 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-404-g52accc779e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 52accc779efe350cb9778005a1fb4aeb9b090456 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc4-4-g602f2118b0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 602f2118b083f998cd7523efcdd5f39689eb15ac (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-400-gad815939c9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ad815939c9b3f604c68a636c88f4842e1ab22129 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-388-gd9cf0ec4d4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via d9cf0ec4d4a942aec3360d66855379f7360ab00d (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc4-2-g2a2c890023

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 2a2c890023c7cfc643d8390a07bffe7676556b32 (commit) via

Re: [CMake] Missing dll on program startup - a way automate it?

Can also add install rules so you get an INSTALL target, and then you can just build that, and everything will end up in the right place. On Thu, Nov 21, 2019 at 3:56 AM Fred Baksik wrote: > Adding the relevant directories to PATH in the debugger or build > environment should allow them to be

Re: [CMake] Missing dll on program startup - a way automate it?

Adding the relevant directories to PATH in the debugger or build environment should allow them to be found. On Wed, Nov 20, 2019, at 3:32 AM, Petr Kmoch wrote: > Hi. > > I haven't used it yet, but I believe the target property >

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-382-g0fff8d653c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 0fff8d653c38e20d9b7a4c026b66f45f8078cb41 (commit) from

Re: [CMake] Missing dll on program startup - a way automate it?

You can also use cmake to just copy the DLLs into the appropriate directory. Here is a snippet from our own projects. #--- #- This copies all the Prebuilt Pipeline files into the Build directory so the help #- works

Re: [CMake] Testing an exe with gtest - possible?

On Wed, 2019-11-20 at 00:54 +0100, cen wrote: > Hi > > I have an existing c++ exe project which I want to test with gtest. > I  > have not yet found an easy way to keep the project as is and test it  > directly since gtest insists (obviously) to link against the code > being  > tested. I found a

Re: [CMake] Missing dll on program startup - a way automate it?

Hi. I haven't used it yet, but I believe the target property https://cmake.org/cmake/help/latest/prop_tgt/VS_DEBUGGER_ENVIRONMENT.html might help you. Petr On Wed, 20 Nov 2019 at 01:02, cen wrote: > Hi > > Perhaps not really a cmake problem but here we go. An exe depends on a > few DLLs which

Re: [CMake] modifying cmake_build_type cflags per target

Am 19.11.19 um 22:51 schrieb Craig Scott: On Tue, Nov 19, 2019 at 10:36 PM Eric Doenges > wrote: Am 19.11.19 um 12:09 schrieb Stéphane Ancelot: Hi, I have a particular target (using swig / jni) that must not have -O3 -NDEBUG flags from Relase

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-381-g5f630a934a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5f630a934aa4b8616aa59988ea70c14065d3a08d (commit) from

[CMake] Missing dll on program startup - a way automate it?

Hi Perhaps not really a cmake problem but here we go. An exe depends on a few DLLs which I ship in the repo so the rest of the devs don't have to build them or fetch them somewhere else. Cmake finds the libraries and project builds just fine, until you run it from VS.. you are welcomed by

[CMake] Testing an exe with gtest - possible?

Hi I have an existing c++ exe project which I want to test with gtest. I have not yet found an easy way to keep the project as is and test it directly since gtest insists (obviously) to link against the code being tested. I found a smart answer on SO to link against object files and that

Re: [CMake] modifying cmake_build_type cflags per target

On Tue, Nov 19, 2019 at 10:36 PM Eric Doenges wrote: > Am 19.11.19 um 12:09 schrieb Stéphane Ancelot: > > Hi, > > I have a particular target (using swig / jni) that must not have -O3 > -NDEBUG flags from Relase build type > > How can I overload this target flags ? > > Since CMAKE__FLAGS_RELEASE

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-380-g9e9787f19a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 9e9787f19a69ed6e0482d29a508548b048dd025d (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-378-g3520208cbd

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 3520208cbd0ebf9f3db1a9711b49286462cd7e54 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-376-ga1d0653fc8

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via a1d0653fc8d8cc07aa130920b86e605e17beaa79 (commit) via

Re: [CMake] Dependencies of an external project

ExternalProject does its work at build time, so too late for find_package which is executed at config time. Have a look at module FetchContent which does its work before config time. Le 19 nov. 2019 à 16:13 +0100, hex , a écrit : > I have an external CMake project that gets exported on install.

[CMake] Dependencies of an external project

I have an external CMake project that gets exported on install. The root project uses it as a package. The external project must be installed prior being used as a package. I can solve this problem by using `ExternalProject` for both projects and declare their dependency. My setup is

Re: [CMake] Build dependent targets

Le mar. 19 nov. 2019 à 11:52, Ellon Paiva a écrit : > Hi Eric, > > On 11/19/19 11:10 AM, Eric Noulard wrote: > > > > Le mar. 19 nov. 2019 à 11:03, Ellon Paiva a écrit : > >> Hi, >> >> I was wondering: is there any way to compile all targets that depend on >> a given target ? (i.e. the

Re: [CMake] modifying cmake_build_type cflags per target

Am 19.11.19 um 12:09 schrieb Stéphane Ancelot: Hi, I have a particular target (using swig / jni) that must not have -O3 -NDEBUG flags from Relase build type How can I overload this target flags ? Since CMAKE__FLAGS_RELEASE does not map to a user-visible target property, you cannot

[CMake] modifying cmake_build_type cflags per target

Hi, I have a particular target (using swig / jni) that must not have -O3 -NDEBUG flags from Relase build type How can I overload this target flags ? Regards, S.Ancelot -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information

Re: [CMake] Build dependent targets

Hi Eric, On 11/19/19 11:10 AM, Eric Noulard wrote: Le mar. 19 nov. 2019 à 11:03, Ellon Paiva > a écrit : Hi, I was wondering: is there any way to compile all targets that depend on a given target ? (i.e. the "dependent targets", if my English

Re: [CMake] Build dependent targets

Le mar. 19 nov. 2019 à 11:03, Ellon Paiva a écrit : > Hi, > > I was wondering: is there any way to compile all targets that depend on > a given target ? (i.e. the "dependent targets", if my English does not > fail). > > In my particular case, I have a huge project that contains many libs and >

[CMake] Build dependent targets

Hi, I was wondering: is there any way to compile all targets that depend on a given target ? (i.e. the "dependent targets", if my English does not fail). In my particular case, I have a huge project that contains many libs and executables, and I would like to check that the targets that

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc4-366-g843936f51b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 843936f51b4f409d3106857a3954ff2db669becd (commit) from

[CMake] [ANNOUNCE] CMake 3.16.0-rc4 is ready for testing

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

[Cmake-commits] CMake annotated tag, v3.16.0-rc4, created. v3.16.0-rc4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The annotated tag, v3.16.0-rc4 has been created at 16e5bdfa421adeb28298484be3d8a2e675eb971c (tag) tagging

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-490-g6eaa355e90

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 6eaa355e90dc5b08e76123dc96386442c18d2528 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-125-gd25d75687d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via d25d75687d3fe53ab19b61b5d671c83d8203f15c (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-488-g9112933a6c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 9112933a6cb398daade678c1bada5e363dcab09c (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-124-g3a87ce6c96

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 3a87ce6c962d2b5b0661d7b611070adf7077b27b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-484-g3bc808fc33

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 3bc808fc3315d459a7d029645a9e892b7abcaa9a (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-122-g4bbd9e9ec4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 4bbd9e9ec4cf234df82f7d25449f3f3a8406979a (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-120-ge64d39eb42

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via e64d39eb42a13f3a8d0e3d005a2936a27a2c8257 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-480-gcbedead9a2

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via cbedead9a25c12272918f1f70c8a1e1417605728 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-118-g1c09b8c164

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 1c09b8c164e0efd8fe82bb783d014e09e0285a0e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-476-g776d1e5e79

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 776d1e5e79ab5194a39ea53252703bf3cc13c118 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-457-gf63d84c37c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via f63d84c37c9ee1ea686369848b5bfc22916e1551 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-111-gfc4f00cbf6

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via fc4f00cbf64c6f192b36e7b9187fc26a1f51a4b4 (commit) via

[CMake] Custom dependencies (gcc -M)

Hi, How do I add dependencies of a C header file to a custom target? Thanks - Niklas -- Powered by kitware.com/cmake Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services Visit other Kitware

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-451-ge56e9c14c5

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e56e9c14c5f06341c101e8de2a4876ecf3f5514f (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-450-gcf598311ce

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via cf598311ce9c6edb2b7d2a1de945ba7f2418c2fb (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-449-gde1d530ef0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via de1d530ef0a638463da87e7a66c26cafc938e986 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-448-g5695b0464b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5695b0464b411746b207da2ee23b8e2d9f8ffec2 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-109-gf8a1b07953

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via f8a1b07953e6bf40da7def8459f8327cb007d2a9 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-436-gb55f605e70

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via b55f605e70f3186e6611f4f84dc246d39453af03 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-429-g10f8197400

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 10f8197400cf0be678444f7400c8739f63096c76 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-107-g330b7b0190

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 330b7b01909e5a6fda0b6fc89f2775953cf6cdc8 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-417-ga10e11fd7c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via a10e11fd7c36a2086223384d35f3d5325ef84f05 (commit) from

Re: [CMake] Making find_package work + compiler flags

Hi, the simplest way AFAIK would be like install(   TARGETS foo EXPORT Foo-config   ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}   LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} ) install(EXPORT Foo-config DESTINATION ${CMAKE_INSTALL_DATADIR}/Foo/cmake) or install(EXPORT Foo-config NAMESPACE foo:

[CMake] Making find_package work + compiler flags

Hi, I'm trying to get started with CMake in a personal project having used other build system previously. The main reason to try out CMake is that CUDA support sucks in Bazel. I see a lot of conflicting information in tutorials and blog posts and I'm trying to avoid going down the rabbit hole

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-416-gaeb95264e0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via aeb95264e02252aba705166dfb8410baff0e715d (commit) from

[CMake] How to specify build output directory path?

Hi I am rather confused about how to specify the output directory. I am working on Windows with the Ninja generator and Microsoft toolset. My default build type is Debug. I am building a library and an executable: add_subdirectory(../Kernel Kernel) add_executable(MyExe ../Kernel/main.cpp) The

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-101-g842605341a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 842605341a6d1c3ca4fe4650f0f1572631cfc6a5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-415-g011693867a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 011693867ac0ee81912cca8e2289b9c584ccfb9b (commit) via

Re: [CMake] Question about list ordering

The list command is what you want. Specifically, list(GET ...) will return the index of a string in the list, and list(INSERT ...) and list(REMOVE_ITEM ...) or list(REMOVE_AT ...) to insert and remove items. Am 13.11.19 um 00:56 schrieb

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-397-ge49d85ae4b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e49d85ae4b5397ec33bcfc6bc7984fedd7dcff11 (commit) from

[CMake] Question about list ordering

Hello everyone, i'm relative new to CMake and i need a function that does change the order of a list. So for example when i have a list like set(LIBS_TO_BUILD "BOOST;EIGEN;PYTHON;GLUT;GLFW;NLOHMANNJSON") i need a function to swap places like listSwapString("GLUT", "GLFW", ${LIBS_TO_BUILD}).

[CMake] MSVC Version Location for VisualStudio Install

All, I have been adding support for VS2019 to our build and ran into some CMake code that was hard coded for a specific version related to MSVC. Specifically, it is the folder under the VS install dir with version like "14.23.28105". It is in the path for where the compiler is found but I can't

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-93-g28bc41ca62

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 28bc41ca62b00d5c265c83436f317f970a4b9a93 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-396-gaa3b99d580

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via aa3b99d58048500c3b24881998b31653178f43ff (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-392-gccd2c2824a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ccd2c2824aea342b66adde1001753181375c49dc (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-91-geae743bf17

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via eae743bf17605c28ee4afd02991d3271efb5c8a9 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-377-g2af4841428

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 2af4841428b7d7e5303d0a0afc3e55958214e22c (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-87-gb197d20c08

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via b197d20c083da1cbfd32e79c4a4c8f36de3a6aae (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-365-g2644ea3c21

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 2644ea3c2123c374558b8007fe97e7e9838ca1a2 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-79-gf90c351e60

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via f90c351e601a98ddb10822d6973dd2fcc140e13e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-352-gc96ba58a5b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c96ba58a5bfee1b98cfcef188b716aca72e406df (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-72-gcba091d3a9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via cba091d3a900d69961ef94a475c3ba1b0cb94453 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-70-g00f5e02060

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 00f5e0206037ceec2d3c33569d1c845fdffa504f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-348-gbec38523de

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via bec38523de60cd7602b0fa89d38356c6f5e7cddd (commit) via

Re: [CMake] CMake link to external library

On Tue, Nov 12, 2019 at 7:39 AM . wrote: > Hi, > I used instruction for CMake linking external library from > https://stackoverflow.com/questions/8774593/cmake-link-to-external-library(for > example) > And it works on Ubuntu 16 only. > > When I try it made on Ubuntu 18 I got problem during start

[CMake] CMake link to external library

Hi, I used instruction for CMake linking external library from  https://stackoverflow.com/questions/8774593/cmake-link-to-external-library(for example) And it works on Ubuntu 16 only. When I try it made on Ubuntu 18 I got problem during start application:  error while loading shared libraries:

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-343-g2dcd7ce4ba

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 2dcd7ce4ba803fa4c4d27526e45e2c9cbb88e49e (commit) from

Re: [CMake] cross-testing support in cmake

On 2019-11-06 11:00 a.m., Andrew Fuller wrote: Does https://cmake.org/cmake/help/latest/prop_tgt/CROSSCOMPILING_EMULATOR.html#prop_tgt:CROSSCOMPILING_EMULATOR do what you're looking for? So it looks like this variable indeed allows me to define a test wrapper script that handles the

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-67-g5e328c6d74

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 5e328c6d74ed6b6470e1df1005d07fe930185b52 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-342-g95555d95aa

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 9d95aa04658a5d656f90f031e9fdea661a02 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-334-ge3aeae7ee8

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e3aeae7ee80bfba17568a529f756eb23ef8269a1 (commit) via

Re: [cmake-developers] CMake removes /DEF: option in CMAKE_SHARED_LINKER_FLAGS

Thank you very much, Brad. I found that WINDOWS_EXPORT_ALL_SYMBOLS was set in my CMakeLists.txt. After I removed it the /DEF parameter from CMAKE_SHARED_LINKER_FLAGS appeared in the linking command. -- Best Regards, Alexander On Fri, 8 Nov 2019 at 14:52, Brad King wrote: > On 11/8/19 5:17 AM,

Re: [CMake] Using CMake with TI armcl and armar

Am 09.11.19 um 00:15 schrieb Samyukta Ramnath: I want to add a CC1352P1_LAUNCHXL_TIRTOS.cmd  file, which has been added in the CCS linker command, but I am unable to include It in my linker command. I tried the following things : set(LINKER_SCRIPT "${LWIP_DIR}/CC1352P1_LAUNCHXL_TIRTOS.cmd")

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-331-geb306700d5

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via eb306700d536849c4125d4a9b84e0bd40b4f2844 (commit) from

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc3-63-gadf863f15e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via adf863f15e348789e4d20e3d2dd792f35d4f4725 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-330-g77241aafb9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 77241aafb9e9f3b12f24a5c19883966614e3b457 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-326-ga9c0959900

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via a9c09599002baa27bdf4f98664829a92ba529240 (commit) from

Re: [CMake] CMake Error Flagged in MSVC Toolchain File

Yeah, I typed it correctly in the actual command and missed the C when copy-pasting it here. Sorry about that. I also want to know if it's possible to use LLVM 10 with the ClangCl toolset in VS2019. The toolchain file itself uses LLVM 8.0.1, but I also have LLVM 10 installed on my computer

Re: [CMake] Suddendly missing members when compiling on macOS Mojave

I managed to fix it. I got confused because recently I updated Xcode, but in facts the problem was completely unrelated: I had a project header file named “math.h”. :) Very noob mistake! Interestingly enough, this bug does not pop-out on Linux (using GCC).  So I just renamed “math.h” to a

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc3-325-g4523e4b326

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 4523e4b3262e81ed179321c154770b20899041c6 (commit) from

Re: [CMake] Using CMake with TI armcl and armar

Hello Eric, Thank you – I was able to get the compile options I expected in the make command when I passed in the Toolchain.cmake file as you had specified in your email. I’m having a few more problems getting the command I want. I’m looking at Code composer studio and here’s the linker

<    1   2   3   4   5   6   7   8   9   10   >