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 to

[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 CMAKE_C_IMPLICIT_LINK_LIBRAR

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 this >> way until I figu

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 learning as I go along

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 in

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 www.kitware.co

[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 Ki

[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 http://stackoverflow.com/questions/31274577/cus

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: add_library(...

[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

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 been deprecated for a w

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

[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 ${FOO_INSTALL

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: https://gist.github

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 someth