Re: [CMake] CMakeLists.txt in different place than source
On Wed, Jun 13, 2018 at 9:46 PM Andrew White
wrote:
> J Decker wrote:
>
> You can define a variable to define the base of the sources
>
> set( SOURCE_ROOT /some/path )
>
>
>
> could be set relative to the current cmake path per cmake that uses those
>
> souces... and then just prefix it
>
>
>
> add_library(my_lib
>
> ${SOURCE_ROOT}/src/a.c
>
> ${SOURCE_ROOT}/include/a.h
>
> )
>
>
>
> Thanks, but that’s approximately exactly what I’m trying to avoid doing.
> I cheat a little, in that I have a macro that will prepend a prefix to
> every element of a list. My motivation is avoiding situations where I add
> the prefix to the files but forget to add the prefix when I call
> target_include_directories or suchlike.
>
>
>
> I’m not sure anything trickier is workable in the CMake model, however.
> For example, hacking CMAKE_CURRENT_SOURCE_DIR might make sense for file
> paths, but if I then call add_subdirectory should it be rooted at the
> CMakeList directory or the source root directory.
>
>
>
CMAKE_CURRENT_LIST_DIR
https://stackoverflow.com/questions/15662497/difference-between-cmake-current-source-dir-and-cmake-current-list-dir
yes that's an option also.
It will be pretty clear there's an error if something is omitted later;
and/or referenced from a different place.
and then it's not just a matter of
> --
>
> Andrew
>
>
> --
>
> 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
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
--
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
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
[CMake] Null alias targets?
I have a library that needs to be built on some platforms but on others is part
of the OS. I'd like to avoid putting "if platform" conditional code in the
places it is used, but instead hide it away in my platform-specific code.
One way to do this is define a variable mylib_targetname in each platform and
add ${mylib_targetname} as a dependency. It can be defined on some platforms
and undefined on others.
It feels cleaner if I could create an alias target MY_NAMESPACE::mylib and
refer to that. This lets me define the dependency without making sure an
environment variable is set, which feels more natural. But in order to make
this work I need a way to express that MY_NAMESPACE::mylib might be
(legitimately) null on some platforms, and I can't figure out how to do this.
Any ideas?
--
Andrew
--
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
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt in different place than source
J Decker wrote:
You can define a variable to define the base of the sources
set( SOURCE_ROOT /some/path )
could be set relative to the current cmake path per cmake that uses those
souces... and then just prefix it
add_library(my_lib
${SOURCE_ROOT}/src/a.c
${SOURCE_ROOT}/include/a.h
)
Thanks, but that’s approximately exactly what I’m trying to avoid doing. I
cheat a little, in that I have a macro that will prepend a prefix to every
element of a list. My motivation is avoiding situations where I add the prefix
to the files but forget to add the prefix when I call
target_include_directories or suchlike.
I’m not sure anything trickier is workable in the CMake model, however. For
example, hacking CMAKE_CURRENT_SOURCE_DIR might make sense for file paths, but
if I then call add_subdirectory should it be rooted at the CMakeList directory
or the source root directory.
--
Andrew
--
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
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v3.11.3-965-gb367da7
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 b367da75c19403b97ce657332d455add05a79928 (commit) from 9eeed4f4d8cfef023a1277d5382032b54c2534f3 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b367da75c19403b97ce657332d455add05a79928 commit b367da75c19403b97ce657332d455add05a79928 Author: Kitware Robot AuthorDate: Thu Jun 14 00:01:10 2018 -0400 Commit: Kitware Robot CommitDate: Thu Jun 14 00:01:10 2018 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 96228d8..2486bdf 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 12) -set(CMake_VERSION_PATCH 20180613) +set(CMake_VERSION_PATCH 20180614) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] cmake in MacPorts environment difficulties
That could be. I'll have to see if I can figure a way to get MacPorts to cough up more information about the commands it is issuing; the MacPorts people ought to know. -- Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com On Wed, Jun 13, 2018 at 4:34 PM, Michael Jackson < mike.jack...@bluequartz.net> wrote: > CMake is looking for .app package and my guess is that the package being > built is a "unix" style installation. If your project depends on just > MacPorts you should be able to just do "make install" after setting the > CMAKE_INSTALL_PREFIX=/opt/local. > > -- > Mike Jackson > > On 6/13/18, 4:17 PM, "CMake on behalf of Randolph Fritz" < > cmake-boun...@cmake.org on behalf of rmfri...@gmail.com> wrote: > > I’ve been trying to add the Radiance lighting simulation package to > the MacPorts package manager, and I am running into cmake problems. I can > build Radiance with cmake from the command line and from the CMake command > line app, but when I write a MacPorts to build it, it falls down on > install. I include the log of errors (the entire log is voluminous.) Does > anyone have any ideas of why this is happening? Any information about what > to tell MacPorts or CMake to get more information? > > Randolph M. Fritz > > > :info:destroot -- fixup_bundle > > :info:destroot -- app='/opt/local/bin/rvu' > > :info:destroot -- libs='/opt/local/var/macports/ > build/_Users_rfritz_MacPorts_science_radiance/radiance/ > work/destroot/opt/local/bin/plugins/imageformats/libqgif. > dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_ > science_radiance/radiance/work/destroot/opt/local/bin/ > plugins/imageformats/libqico.dylib;/opt/local/var/macports/ > build/_Users_rfritz_MacPorts_science_radiance/radiance/ > work/destroot/opt/local/bin/plugins/imageformats/libqjpeg. > dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_ > science_radiance/radiance/work/destroot/opt/local/bin/ > plugins/imageformats/libqtiff.dylib;/opt/local/var/macports/ > build/_Users_rfritz_MacPorts_science_radiance/radiance/ > work/destroot/opt/local/bin/plugins/platforms/libqcocoa.dylib' > > :info:destroot -- dirs='/opt/local/libexec/qt5/lib;/opt/local/lib' > > :info:destroot -- ignoreItems='' > > :info:destroot -- warning: *NOT* handled - directory/file does not > exist... > > :info:destroot CMake Error at /opt/local/share/cmake-3.11/ > Modules/BundleUtilities.cmake:966 (message): > > :info:destroot error: fixup_bundle: not a valid bundle > > :info:destroot Call Stack (most recent call first): > > :info:destroot InstallRules/dependencies.cmake:14 (fixup_bundle) > > :info:destroot InstallRules/cmake_install.cmake:36 (include) > > :info:destroot cmake_install.cmake:47 (include) > > :info:destroot -- fixup_bundle: done > > :info:destroot make: *** [install/fast] Error 1 > > :info:destroot make: Leaving directory `/opt/local/var/macports/ > build/_Users_rfritz_MacPorts_science_radiance/radiance/work/build' > > :info:destroot Command failed: cd "/opt/local/var/macports/ > build/_Users_rfritz_MacPorts_science_radiance/radiance/work/build" && > /usr/bin/make -w install/fast DESTDIR=/opt/local/var/ > macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot > > > :info:destroot Exit code: 2 > > -- > > 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 > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > > > > -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] cmake in MacPorts environment difficulties
CMake is looking for .app package and my guess is that the package being built is a "unix" style installation. If your project depends on just MacPorts you should be able to just do "make install" after setting the CMAKE_INSTALL_PREFIX=/opt/local. -- Mike Jackson On 6/13/18, 4:17 PM, "CMake on behalf of Randolph Fritz" wrote: I’ve been trying to add the Radiance lighting simulation package to the MacPorts package manager, and I am running into cmake problems. I can build Radiance with cmake from the command line and from the CMake command line app, but when I write a MacPorts to build it, it falls down on install. I include the log of errors (the entire log is voluminous.) Does anyone have any ideas of why this is happening? Any information about what to tell MacPorts or CMake to get more information? Randolph M. Fritz > :info:destroot -- fixup_bundle > :info:destroot -- app='/opt/local/bin/rvu' > :info:destroot -- libs='/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqgif.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqico.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqjpeg.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqtiff.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/platforms/libqcocoa.dylib' > :info:destroot -- dirs='/opt/local/libexec/qt5/lib;/opt/local/lib' > :info:destroot -- ignoreItems='' > :info:destroot -- warning: *NOT* handled - directory/file does not exist... > :info:destroot CMake Error at /opt/local/share/cmake-3.11/Modules/BundleUtilities.cmake:966 (message): > :info:destroot error: fixup_bundle: not a valid bundle > :info:destroot Call Stack (most recent call first): > :info:destroot InstallRules/dependencies.cmake:14 (fixup_bundle) > :info:destroot InstallRules/cmake_install.cmake:36 (include) > :info:destroot cmake_install.cmake:47 (include) > :info:destroot -- fixup_bundle: done > :info:destroot make: *** [install/fast] Error 1 > :info:destroot make: Leaving directory `/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/build' > :info:destroot Command failed: cd "/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/build" && /usr/bin/make -w install/fast DESTDIR=/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot > :info:destroot Exit code: 2 -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] cmake in MacPorts environment difficulties
I’ve been trying to add the Radiance lighting simulation package to the MacPorts package manager, and I am running into cmake problems. I can build Radiance with cmake from the command line and from the CMake command line app, but when I write a MacPorts to build it, it falls down on install. I include the log of errors (the entire log is voluminous.) Does anyone have any ideas of why this is happening? Any information about what to tell MacPorts or CMake to get more information? Randolph M. Fritz > :info:destroot -- fixup_bundle > :info:destroot -- app='/opt/local/bin/rvu' > :info:destroot -- > libs='/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqgif.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqico.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqjpeg.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/imageformats/libqtiff.dylib;/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot/opt/local/bin/plugins/platforms/libqcocoa.dylib' > :info:destroot -- dirs='/opt/local/libexec/qt5/lib;/opt/local/lib' > :info:destroot -- ignoreItems='' > :info:destroot -- warning: *NOT* handled - directory/file does not exist... > :info:destroot CMake Error at > /opt/local/share/cmake-3.11/Modules/BundleUtilities.cmake:966 (message): > :info:destroot error: fixup_bundle: not a valid bundle > :info:destroot Call Stack (most recent call first): > :info:destroot InstallRules/dependencies.cmake:14 (fixup_bundle) > :info:destroot InstallRules/cmake_install.cmake:36 (include) > :info:destroot cmake_install.cmake:47 (include) > :info:destroot -- fixup_bundle: done > :info:destroot make: *** [install/fast] Error 1 > :info:destroot make: Leaving directory > `/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/build' > :info:destroot Command failed: cd > "/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/build" > && /usr/bin/make -w install/fast > DESTDIR=/opt/local/var/macports/build/_Users_rfritz_MacPorts_science_radiance/radiance/work/destroot > > :info:destroot Exit code: 2 -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] Refer existing xcode project from cmake project
Hello, I want to add sub project to xcode generated project. I am adding xcodeproj folder as a source file and it looks like the sub project is added correctly to the parent project. But I can not add target dependency from the parent to the sub project target. Parent project is generated from cmake and subproject is existing xcode project. Can anyone help how can add target dependency? Regards, Kaloyan Donev -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, release, updated. v3.11.3-935-gef5e2e8
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 ef5e2e8a62982ebccf4883fc7a01cdb66f8ca183 (commit) via 985c78c7e1ec93662691c4b078dad847b715a991 (commit) via 93fe9fc1a218ac96756cf8181a2d3421ab090192 (commit) via 0c2fb4c8964b6164c44e8641c8c9225369c0228b (commit) via 4e6ff0ae247847ae5a2996d59106d8dc4aacced4 (commit) via 276e369813f100562c3e22020635552edfb722a2 (commit) via f024f4f8a0f37d9c4904f2a968b3ed309146650d (commit) via 88dd5dc9ff405ee5bd63b15ea1e5219e5d029e12 (commit) via 3dd046a84b3fae99a36b7f7680310344b986b5a9 (commit) via 156138d5f1d15a79f86db64bbe2dd6043fd3b43f (commit) from 1f3221f365f269f3356de0ad0112cf68e4831fe6 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - --- Summary of changes: Help/release/3.12.rst|3 ++ Modules/UseSWIG.cmake| 25 -- Source/CMakeInstallDestinations.cmake|7 +++- Source/cmSystemTools.cxx |3 +- Tests/UseSWIG/BasicConfiguration.cmake |4 +++ Tests/UseSWIG/BasicCsharp/CMakeLists.txt | 21 Tests/UseSWIG/CMakeLists.txt | 14 Tests/UseSWIG/runme.cs | 54 ++ Utilities/Sphinx/CMakeLists.txt | 29 +++- bootstrap|8 + 10 files changed, 155 insertions(+), 13 deletions(-) create mode 100644 Tests/UseSWIG/BasicCsharp/CMakeLists.txt create mode 100644 Tests/UseSWIG/runme.cs hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.11.3-964-g9eeed4f
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 9eeed4f4d8cfef023a1277d5382032b54c2534f3 (commit) via ef5e2e8a62982ebccf4883fc7a01cdb66f8ca183 (commit) via 985c78c7e1ec93662691c4b078dad847b715a991 (commit) via 93fe9fc1a218ac96756cf8181a2d3421ab090192 (commit) via aa155de8607d6faeace64dfb47a469d9329a4fcd (commit) via 0247f6836c9318396c91ec01dc682b12185a37e4 (commit) via b7b4ace2bebd7d063b38c4537e67050628dc1c51 (commit) via 3b7da49d55691eeb9177ab25b047440decaed77a (commit) via 49c30fc65c7f93f15d9368112b659f43c387eb1e (commit) via 0c2fb4c8964b6164c44e8641c8c9225369c0228b (commit) via 051e0be742071fdd5eca2bc90f372422f27fd1fa (commit) via 276e369813f100562c3e22020635552edfb722a2 (commit) via f024f4f8a0f37d9c4904f2a968b3ed309146650d (commit) via 88dd5dc9ff405ee5bd63b15ea1e5219e5d029e12 (commit) via 3dd046a84b3fae99a36b7f7680310344b986b5a9 (commit) via 156138d5f1d15a79f86db64bbe2dd6043fd3b43f (commit) from 38e4246f37b832b88437e83710348c174be02508 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9eeed4f4d8cfef023a1277d5382032b54c2534f3 commit 9eeed4f4d8cfef023a1277d5382032b54c2534f3 Merge: aa155de ef5e2e8 Author: Brad King AuthorDate: Wed Jun 13 10:52:58 2018 -0400 Commit: Brad King CommitDate: Wed Jun 13 10:52:58 2018 -0400 Merge branch 'release-3.12' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa155de8607d6faeace64dfb47a469d9329a4fcd commit aa155de8607d6faeace64dfb47a469d9329a4fcd Merge: 0247f68 276e369 Author: Brad King AuthorDate: Wed Jun 13 14:50:08 2018 + Commit: Kitware Robot CommitDate: Wed Jun 13 10:50:14 2018 -0400 Merge topic 'sphinx-info' 276e369813 Utilities/Sphinx: Add option to build and install Info manual Acked-by: Kitware Robot Merge-request: !2146 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0247f6836c9318396c91ec01dc682b12185a37e4 commit 0247f6836c9318396c91ec01dc682b12185a37e4 Merge: b7b4ace 0c2fb4c Author: Brad King AuthorDate: Wed Jun 13 14:48:37 2018 + Commit: Kitware Robot CommitDate: Wed Jun 13 10:48:51 2018 -0400 Merge topic 'UseSWIG-csharp-variant' 0c2fb4c896 UseSWIG: Add CSHARP variant for wrapper files Acked-by: Kitware Robot Merge-request: !2137 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b7b4ace2bebd7d063b38c4537e67050628dc1c51 commit b7b4ace2bebd7d063b38c4537e67050628dc1c51 Merge: 3b7da49 88dd5dc Author: Brad King AuthorDate: Wed Jun 13 14:47:57 2018 + Commit: Kitware Robot CommitDate: Wed Jun 13 10:48:04 2018 -0400 Merge topic 'UseSWIG-fix-genex' 88dd5dc9ff UseSWIG: add support for generator expressions Acked-by: Kitware Robot Merge-request: !2143 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3b7da49d55691eeb9177ab25b047440decaed77a commit 3b7da49d55691eeb9177ab25b047440decaed77a Merge: 49c30fc 156138d Author: Brad King AuthorDate: Wed Jun 13 14:46:58 2018 + Commit: Kitware Robot CommitDate: Wed Jun 13 10:47:06 2018 -0400 Merge topic 'UseSWIG-handle-SWIG_MODULE_NAME' 156138d5f1 UseSWIG: Fix handling of `SWIG_MODULE_NAME` source file property Acked-by: Kitware Robot Merge-request: !2145 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=49c30fc65c7f93f15d9368112b659f43c387eb1e commit 49c30fc65c7f93f15d9368112b659f43c387eb1e Merge: 38e4246 051e0be Author: Brad King AuthorDate: Wed Jun 13 10:45:29 2018 -0400 Commit: Brad King CommitDate: Wed Jun 13 10:45:29 2018 -0400 Merge branch 'release-3.11' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=051e0be742071fdd5eca2bc90f372422f27fd1fa commit 051e0be742071fdd5eca2bc90f372422f27fd1fa Merge: 2ccd426 4e6ff0a Author: Brad King AuthorDate: Tue Jun 12 11:19:07 2018 -0400 Commit: Brad King CommitDate: Tue Jun 12 11:19:07 2018 -0400 Merge branch 'restore-windows-resources-through-link' into release-3.11 Merge-request: !2147 --- Summary of changes: Help/release/3.12.rst|3 ++ Modules/UseSWIG.cmake| 25 -- Source/CMakeInstallDestinations.cmake|7 +++- Tests/UseSWIG/BasicConfiguration.cmake |4 +++ Tests/UseSWIG/BasicCsharp/CMakeLists.txt | 21 Tests/UseSWIG/CMakeLists.txt | 14 Tests/UseSWIG/runme.cs | 54 ++
[Cmake-commits] CMake branch, master, updated. v3.11.3-948-g38e4246
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 38e4246f37b832b88437e83710348c174be02508 (commit)
via 4e6ff0ae247847ae5a2996d59106d8dc4aacced4 (commit)
from cfac183295d9ce18403b0aa22c038a814f06832f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=38e4246f37b832b88437e83710348c174be02508
commit 38e4246f37b832b88437e83710348c174be02508
Merge: cfac183 4e6ff0a
Author: Brad King
AuthorDate: Wed Jun 13 14:44:22 2018 +
Commit: Kitware Robot
CommitDate: Wed Jun 13 10:44:45 2018 -0400
Merge topic 'restore-windows-resources-through-link'
4e6ff0ae24 Windows: Restore support for running CMake through a symlink
Acked-by: Kitware Robot
Merge-request: !2147
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4e6ff0ae247847ae5a2996d59106d8dc4aacced4
commit 4e6ff0ae247847ae5a2996d59106d8dc4aacced4
Author: Brad King
AuthorDate: Tue Jun 12 11:02:28 2018 -0400
Commit: Brad King
CommitDate: Tue Jun 12 11:15:50 2018 -0400
Windows: Restore support for running CMake through a symlink
The change in commit v3.11.3~3^2 (cmSystemTools: Revert GetRealPath
implementation on Windows, 2018-05-29) broke the feature added by commit
v3.11.0-rc1~64^2 (Windows: Add support for running CMake tools through a
symlink, 2018-01-21). Use `GetRealPathResolvingWindowsSubst` in the
latter code path to restore it.
Fixes: #17882
diff --git a/Source/cmSystemTools.cxx b/Source/cmSystemTools.cxx
index 6f326de..9575c05 100644
--- a/Source/cmSystemTools.cxx
+++ b/Source/cmSystemTools.cxx
@@ -2117,7 +2117,8 @@ void cmSystemTools::FindCMakeResources(const char* argv0)
wchar_t modulepath[_MAX_PATH];
::GetModuleFileNameW(NULL, modulepath, sizeof(modulepath));
std::string path = cmsys::Encoding::ToNarrow(modulepath);
- std::string realPath = cmSystemTools::GetRealPath(path, NULL);
+ std::string realPath =
+cmSystemTools::GetRealPathResolvingWindowsSubst(path, NULL);
if (realPath.empty()) {
realPath = path;
}
---
Summary of changes:
Source/cmSystemTools.cxx |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] CMakeLists.txt in different place than source
On Tue, Jun 12, 2018 at 7:22 PM Andrew White
wrote:
> I have a situation where I want my CMakeLists.txt in a different place
> than my source.
>
> e.g.:
>
> /some/path/project/CMakeLists.txt
> /other/path/source/src/a.c
> /other/path/source/include/a.h
>
> Is there an easy way to say "process this CMakeLists.txt as if it were in
> /other/path/source" (at least as far as file paths are concerned)?
>
> e.g.:
>
> add_library(my_lib
> src/a.c
> include/a.h
> )
>
> target_include_directories(my_lib PUBLIC include)
>
> I know I can add a full path prefix to every file, but there are a lot of
> them. I'm hoping for a shortcut.
>
You can define a variable to define the base of the sources
set( SOURCE_ROOT /some/path )
could be set relative to the current cmake path per cmake that uses those
souces... and then just prefix it
add_library(my_lib
${SOURCE_ROOT}/src/a.c
${SOURCE_ROOT}/include/a.h
)
>
> --
> Andrew
>
>
> --
>
> 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
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
--
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
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
Re: [cmake-developers] Using pkgconf
On 06/12/2018 12:11 PM, Paul Fultz II via cmake-developers wrote: > https://github.com/pkgconf/pkgconf > > CMake could use pkgconf internally The license looks MIT-like. Please confirm that it is at least BSD-3 compatible. > find_package(zlib CONF) > > And this would look up zlib using pkgconfig An important distinction is that `find_package` is meant for whole packages that may contain multiple libraries and components, while IIUC a `.pc` file is equivalent to a single CMake target. We'll need a way to reconcile that. Does pkgconfig have conventions for meta-packages that cover multiple components? Also, how should version matching work? Thanks, -Brad -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
Re: [CMake] cmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
On 06/13/2018 04:22 AM, Gerhard Olsson wrote: > The build works on my PC, but not on the Jenkins server running Windows > Server 2012R2: cmake.exe: error while loading shared libraries: ?: cannot > open shared object file: No such file or directory > > Any steps required to get a binary that runs on the server too? Likely you built against a MSVC C run time library that is not installed on the server. You'd need to install the corresponding MSVC redist package on that server, or build a CMake that is statically linked to the runtime. Or, you could try a nightly binary that is already built that way: https://cmake.org/files/dev/?C=M;O=D -Brad -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [cmake-developers] cmake on AIX
Hi Brad, With cmake 3.2.3 , Séna is able to build MariaDB. However, with version 3.11.1 , we have issues (core or hang of cmake, and other issues). Investigating. We'll move to 3.11.3 asap in order to see if we face the same issues. Cordialement, Tony Reix ATOS / Bull SAS ATOS Expert IBM Coop Architect & Technical Leader Office : +33 (0) 4 76 29 72 67 1 rue de Provence - 38432 Échirolles - France www.atos.net De : Brad King [brad.k...@kitware.com] Envoyé : mardi 12 juin 2018 15:44 À : REIX, Tony; cmake-developers@cmake.org Cc : APEKE, SENA (ext) Objet : Re: [cmake-developers] cmake on AIX On 06/12/2018 09:36 AM, REIX, Tony wrote: > I never saw any package built on AIX using pthread or ppc64/pthread > We have to understand why cmake is different. We use C++11 std::thread. It requires GCC's -pthread flag on AIX, and that flag changes the standard library that is used. -Brad -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[CMake] cmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
Trying to build lastest release, to get a preview for 3.12-rc1 that should be released soon. The specific reason is to fix a problem with linking failing due to response files not generated: http://cmake.3232098.n2.nabble.com/No-RSP-FILE-if-generating-in-a-path-that-contains-quot-quot-tc7597671.html https://gitlab.kitware.com/cmake/cmake/merge_requests/1983 https://gitlab.kitware.com/cmake/cmake/issues/18075 The build setup is done without changes on my PC (Win7-x64). The build works on my PC, but not on the Jenkins server running Windows Server 2012R2: cmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory Any steps required to get a binary that runs on the server too? /Gerhard -- 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 CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
