Re: [CMake] Shared library for a executable

Hi Tamás, On Mon, Jan 25, 2016 at 7:02 PM, Tamás Kenéz wrote: > Gonzalo, Ray, > > I think your approaches are not in accordance with some CMake best practices > (or at least what I believe they are). Thank you for looking over my web site! I welcome comments since I am

[cmake-developers] [CMake 0015934]: There's no way to test whether a given *linker* flag works

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15934 == Reported By:Guy Harris Assigned To:

[Cmake-commits] CMake branch, master, updated. v3.4.3-908-ge7eab0e

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20160125) +set(CMake_VERSION_PATCH 20160126) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[CMake] How to override CMAKE_C_IMPLICIT_LINK_LIBRARIES

I have the need to link a shared library to all the targets without modifying the CMakeLists.txt(for example, tcmalloc.so). I used the command: # cmake -DCMAKE_C_IMPLICIT_LINK_LIBRARIES:STRING=tcmalloc However, It didn't work. I used the message() command to print the

Re: [CMake] Shared library for a executable

Hi Gonzalo, On Mon, Jan 25, 2016 at 5:22 PM, Gonzalo wrote: > > > El 22/01/16 a las 10:50, Raymond Wan escribió: >> >> Hi Gonzalo, >> >> I recently tried doing this and wrote it up as a record for myself. >> Of course, I don't know if it's the right way, but I'm doing it

Re: [CMake] How to override CMAKE_C_IMPLICIT_LINK_LIBRARIES

On 01/26/2016 06:35 AM, 陆秋文 wrote: I have the need to link a shared library to all the targets without modifying the CMakeLists.txt(for example, tcmalloc.so). I used the command: # cmake -DCMAKE_C_IMPLICIT_LINK_LIBRARIES:STRING=tcmalloc However, It didn't work. I used the message() command

Re: [cmake-developers] [CMake] FIND_PROGRAM fails to find file without 'r' bit set

On 01/25/2016 08:27 AM, Ben Boeckel wrote: > It's both :) . FileExists is implemented using access() rather than > something like lstat(), so that would indeed be not a "program" since > the file doesn't "exist". > > It was on my list to fix, but the backwards compatibility argument > (IIRC) made

Re: [CMake] PROPERTY for list of link libraries

Thanks. Upgrading cmake right now is problematic. On Mon, Jan 25, 2016 at 4:33 AM, Tamás Kenéz wrote: > I think you need something like CMakeExpandImportedTargets.cmake ( > https://cmake.org/cmake/help/latest/module/CMakeExpandImportedTargets.html). > But that module has

Re: [cmake-developers] [CMake] FIND_PROGRAM fails to find file without 'r' bit set

On Mon, Jan 25, 2016 at 16:06:47 +0300, Vyacheslav Barinov wrote: > I try to detect paths to some tools using CMake and got the following problem: > if the tool I try to check has 611 (-rw--x--x) rights FIND_PROGRAM reports the > file does not exists. > > For instance my /bin/mount in Gentoo has

[Cmake-commits] CMake branch, next, updated. v3.4.2-2097-g26aec99

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, next has been updated via 26aec99782f958f3a048e7074be1f5b9e8592426 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.4.2-2-g7b8bec7

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-908-gf9cc671

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

Re: [CMake] add_library object argument question

Hi, the name given after the : in the TARGET_OBJECTS generator expression is the logical (CMake) name of a target. There's no scoping in target names, they're all at the same global scope. So if you have this: add_library(A OBJECT ...) then you will access its objects like this:

[cmake-developers] [CMake] FIND_PROGRAM fails to find file without 'r' bit set

Hello, I try to detect paths to some tools using CMake and got the following problem: if the tool I try to check has 611 (-rw--x--x) rights FIND_PROGRAM reports the file does not exists. For instance my /bin/mount in Gentoo has such setup and therefore I can use it from shell but can't detect it

[Cmake-commits] CMake branch, next, updated. v3.4.2-2100-g9b24c2f

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, next has been updated via 9b24c2fbefae8427a67392ca1f92a733c60496d9 (commit) via

[cmake-developers] CMake 3.5 feature freeze on 2016-02-01

Hi Folks, The feature freeze in 'master' for CMake 3.5 will be on Feb 1, 2016. In order to get 'master' ready to branch for 3.5, 'next' is now frozen to new features. After 3.5 is branched I'll announce when post-3.5 development in 'next' is open. Meanwhile the following types of changes are

[Cmake-commits] CMake branch, master, updated. v3.4.2-904-g9722f8f

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

[Cmake-commits] CMake branch, master, updated. v3.4.2-906-g0586f17

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2094-ga0771e0

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, next has been updated via a0771e09b7d1fa613ffa19dfb5d3dadf6014fc7e (commit) via

Re: [cmake-developers] CMake daemon for user tools

On 10-Jan-16 2:10 PM, Stephen Kelly wrote: Hello, I've been working on adding a daemon mode for cmake to provide information to user tools - such as IDEs - about the buildsystem. Following the discussion about providing metadata for IDEs to consume I proposed creating a long-running process

[Cmake-commits] CMake branch, dashboard, updated. cb56d71de1bd40e06db17cb0266d1fbeabea75a3

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, dashboard has been updated via cb56d71de1bd40e06db17cb0266d1fbeabea75a3 (commit) via

[CMake] add_library object argument question

Hi In a library project there are two level of subdirectories that contain modules to be included into the main library. In other words, directory lib contains subdirectories foo and bar Subdirectory foo contains A and B. Subdirectory bar contains C and D. All of the objects from A, B, C and D

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

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.4.3 has been created at a1ecc5d06c1f86f31da8a0b3a8d58c06aa77417f (tag) tagging

[CMake] making a custom target like add_library()

I create a DLL and import library via custom commands, but for my purposes right now, I need these libraries to be treated as if they were generated with add_library() (for the project I am workingon where I get transitive dependencies); I read this

[cmake-developers] [ANNOUNCE] CMake 3.4.3 available for download

We are pleased to announce that CMake 3.4.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.4.3 since 3.4.2: Brad

[CMake] [ANNOUNCE] CMake 3.4.3 available for download

We are pleased to announce that CMake 3.4.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.4.3 since 3.4.2: Brad

[cmake-developers] [ANNOUNCE] cmake-unit - A new unit testing framework for CMake

Hi all, By way of introduction you might remember me as a maintainer of Compiz between 2009 and 2012, which is the window and compositing manager still used by Ubuntu today. We used CMake quite heavily in Compiz and so I've learned a great deal about it. Over the last two years I've been working

Re: [cmake-developers] CMake daemon for user tools

> -Original Message- > From: Milian Wolff [mailto:m...@milianw.de] > Sent: Saturday, January 23, 2016 15:41 > To: cmake-developers@cmake.org > Cc: James Johnston > Subject: Re: [cmake-developers] CMake daemon for user tools > > You are aware that modern std::string is SSO'ed? I'm running

[Cmake-commits] CMake branch, release, updated. v3.4.2-3-g0aef6f2

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 0aef6f2412177a236deb292654402518777f3cb0 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.4.2-910-gc4e1bc6

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

[Cmake-commits] CMake branch, next, updated. v3.4.2-2102-gc220f4e

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, next has been updated via c220f4e80728c2b39db6d375c0a8d9667769cd08 (commit) via

Re: [CMake] [ANNOUNCE] CMake 3.4.3 available for download

On 25/01/2016 04:36 p.m., Robert Maynard wrote: We are pleased to announce that CMake 3.4.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Brad, Does this one have the fix for the FLTK_WRAP_UI? -- Powered by

Re: [cmake-developers] Anyone going to FOSDEM?

Benjamin Eikel wrote: > Hi Gregor, > > Am Mittwoch, 30. Dezember 2015, 14:33:08 schrieb Gregor Jasny via cmake- > developers: >> Hello, >> >> I wonder if any of you CMake Developers go to FOSDEM [1] this year? > > I am not a CMake developer, but, more or less, an advanced user, but I > will go

Re: [CMake] Library target names and the ExternalProject_Add command

ExternalProject makes no assumptions about what is being built. It could just be a collection of executables, or maybe nothing is built at all. It is up to the project being built to provide facilities for accessing its targets in a platform-independent way. For example, the external project can

Re: [CMake] Shared library for a executable

El 22/01/16 a las 10:50, Raymond Wan escribió: Hi Gonzalo, I recently tried doing this and wrote it up as a record for myself. Of course, I don't know if it's the right way, but I'm doing it this way until I figure out a better way... See if this helps and let me know if you figure out

Re: [CMake] PROPERTY for list of link libraries

I think you need something like CMakeExpandImportedTargets.cmake ( https://cmake.org/cmake/help/latest/module/CMakeExpandImportedTargets.html). But that module has been deprecated for a while and does not support some newer CMake features. Instead, feel free to try out my fork:

Re: [cmake-developers] CMake Daemon blog

That's great and really does open a new world for IDEs! Tamas On Sun, Jan 24, 2016 at 11:44 PM, Stephen Kelly wrote: > Hi, > > I just made a blog and video about the advanced features and possibilities > that a daemon mode for CMake can bring: > >

[CMake] Library target names and the ExternalProject_Add command

Hello, I use the ExternalProject_Add command to download and build a static library called 'foo.a'. I build another library 'bar' which depends on 'foo.a'. For the moment, I use the target_link_libraries command to create a link between foo and bar: target_link_libraries(bar

Re: [CMake] Shared library for a executable

Gonzalo, Ray, I think your approaches are not in accordance with some CMake best practices (or at least what I believe they are). Please take a look at Ray's example after a heavy refactor: https://github.com/tamaskenez/cmake-2016-jan-21-shared-lib-exe These are the things I changed: - In your