[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-87-g0671f71d70

t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index beeb0a6dac..f129c3aa18 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,7 +1,7 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 16) -set(CMake_VERSION_PATCH 2019

Re: [CMake] CMake link order

Hello, I have always used all of the libraries at once to the TARGET_LINK_LIBRARIES command. In the following example, the link line order appears the same as the libraries are listed on the line. TARGET_LINK_LIBRARIES(devsim_tcl ${LIBRARIES} ${TCL_ARCHIVE} ${SUPERLU_ARCHIVE} ${BLAS_ARCHIVE}

Re: [CMake] CMake link order

Hey all, I face a similar problem when constructing a correct (and predictable) link order for Linux and Cygwin. It would be of great help, if there is some documentation. In particular, I would raise two question     1) when does the link order change?     2) when does a clean up happen and in

Re: [CMake] CMake link order

On Fri, Oct 18, 2019, at 11:55 AM, Fred Baksik wrote: > > In target_link_libraries it states that "The library dependency graph is > normally acyclic (a DAG)". I recall from my own experience that the DAG is > not always created the same way when generating the project. It has to do > with

Re: [CMake] CMake link order

On Fri, Oct 18, 2019, at 6:24 AM, Bon, William wrote: > Hello, > > we are facing an issue while using cmake and we have no idea how to solve or > debug it. > We have a complex and huge project (about 50 subdirectories and dependencies > everywhere), and we are facing issue regarding the link

[CMake] CMake link order

Hello, we are facing an issue while using cmake and we have no idea how to solve or debug it. We have a complex and huge project (about 50 subdirectories and dependencies everywhere), and we are facing issue regarding the link order. There is a lot of dependencies between those projects, and to

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

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-rc2 has been created at 371dbf3c152a397447bfae8ddff298b64b01b83b (tag) tagging

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-49-g92780281c2

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 92780281c2e8a46223b262b152caa9c8329373b1 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-135-g493c4e781a

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 493c4e781a35a92c5c912b22493b84de750b1fe1 (commit) via

[CMake] setting rpath in executable in build directory

Hello, I have the following scenario. I have gcc 9.2.0 and boost 1.71.0 installed in /opt/ZS/deps/... directory, built for both arm and x86_64. I can build programs using them just fine and they run as expected provided -Wl,-rpaht,/opt/ZS/deps... is added to g++ command line. Now I'm trying to

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-133-gfdb41a5102

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 fdb41a5102e1fef50fb918eba5f84cfc19a62734 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-48-g6dedb97420

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 6dedb9742094470196698a5009441e3860e61f2a (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-126-gc867981c9d

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 c867981c9d9bc8548d34f726940cd50b8d05d71c (commit) via

Re: [CMake] Help request for hierarchical directory example

Hi Eric Thanks very much for your answer. I understand now. David On Fri, Oct 18, 2019 at 12:57 PM Eric Noulard wrote: > > > Le ven. 18 oct. 2019 à 12:53, David Aldrich > a écrit : > >> Hi >> >> >> >> I'm learning how to use hierarchical directories in CMake and am trying >> to get an

Re: [CMake] Help request for hierarchical directory example

Le ven. 18 oct. 2019 à 12:53, David Aldrich a écrit : > Hi > > > > I'm learning how to use hierarchical directories in CMake and am trying to > get an example to work that I saw on YouTube. The example isn't doing what > I expect so I would be grateful for some help in understanding why. > > > >

[CMake] Help request for hierarchical directory example

Hi I'm learning how to use hierarchical directories in CMake and am trying to get an example to work that I saw on YouTube. The example isn't doing what I expect so I would be grateful for some help in understanding why. I am running CMake 3.10.2 on Ubuntu 18.04 (Microsoft WSL) and using