[CMake] Building an external library based on autotools

2013-03-21 Thread Lucas Soltic
the most important to me, because I won't be modifying the FFmpeg sources more than once every few months. And the FFmpeg sources are already in my repo so I've no need for automatic download. Regards, Lucas SOLTIC P.S.: details about the portable Bash launcher for those who'd like to know

[CMake] How to install files produced by custom targets

2013-09-06 Thread Lucas Soltic
Hello, Considering that I have a custom target that outputs some libraries and these libraries were built using configure+make. The custom library is based on autotools. Configure + make are executed by a custom command in the custom target. Is it possible to add a CMake install rule that

[CMake] Fwd: How to install files produced by custom targets

2013-09-06 Thread Lucas Soltic
Woops wrong target email. So just so that anyone can read.. here it is: Début du message réexpédié : De : Lucas Soltic lucas.sol...@orange.fr Objet : Rép : [CMake] How to install files produced by custom targets Date : 6 septembre 2013 19:15:27 UTC+02:00 À : Petr Kmoch petr.km...@gmail.com

[CMake] Adding unused files to the generated project

2013-09-22 Thread Lucas Soltic
Hello, Is it possible to add files that do not belong to any add_executable/library so that they're visible in the IDE but not used for building? That way I could easily work with the generated project on any useful file, even if it's not directly used to produce binaries (for example, editing

[CMake] How to tell an executable where to look for libraries it depends on

2014-01-23 Thread Lucas Soltic
Hello, Is there a CMake rule to tell an executable where to look for its dynamic libraries when running? So that the dependencies are correctly loaded at runtime. Regards, Lucas SOLTIC -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http

[CMake] CMAKE_RUNTIME_OUTPUT_DIRECTORY inconsistent between make and Xcode

2014-03-05 Thread Lucas Soltic
Hello, I have noticed an annoying difference between Xcode and make as far as the output directory is concerned. I have added the following to my CMakeLists.txt: set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin) set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)

[CMake] Reliable binaries output directory

2014-03-07 Thread Lucas Soltic
Hello, Is there a way to know exactly (through a CMake variable or command) where the binaries will be put? I've defined CMAKE_RUNTIME_OUTPUT_DIRECTORY to put all the executables in the same directory, but some generators will use a Debug/Release subdirectory of this variable's value, whereas

Re: [CMake] CMAKE_RUNTIME_OUTPUT_DIRECTORY inconsistent between make and Xcode

2014-03-09 Thread Lucas Soltic
Le 9 mars 2014 à 21:19, jmerkow jmer...@gmail.com a écrit : I am having a similar issue. I generate a number of scripts I configure with the path to the executables. This path is the same when using make, but with XCode or MSVSC they append the build type (Debug, Release, RelWithDebInfo,

[CMake] How to use LINK_INTERFACE_LIBRARIES

2014-05-24 Thread Lucas Soltic
Hello! I'm having a hard time at properly using LINK_INTERFACE_LIBRARIES. From what I understood, setting this property empty for a target avoids transitive dependencies linking. But whatever I try, it doesn't work. I have created a lib A linked against lib B. I'm also creating an exe linked

Re: [CMake] How to use LINK_INTERFACE_LIBRARIES

2014-05-24 Thread Lucas Soltic
Le 24 mai 2014 à 18:45, Nils Gladitz nilsglad...@gmail.com a écrit : On 24.05.2014 18:15, Lucas Soltic wrote: Hello! I'm having a hard time at properly using LINK_INTERFACE_LIBRARIES. From what I understood, setting this property empty for a target avoids transitive dependencies linking

[CMake] find_library and caching

2014-06-15 Thread Lucas Soltic
Hello, I use a FindSomeLib.cmake script for my project, for which there is a variable (let's call it LINK_STATIC) to define if one wants to link against SomeLib statically. The default is to look for dynamic libraries. The issue is that when first running CMake's configure, the user may

Re: [CMake] find_library and caching

2014-06-15 Thread Lucas Soltic
Le 15 juin 2014 à 20:19, Nils Gladitz nilsglad...@gmail.com a écrit : On 15.06.2014 19:33, Lucas Soltic wrote: I use a FindSomeLib.cmake script for my project, for which there is a variable (let's call it LINK_STATIC) to define if one wants to link against SomeLib statically. The default

Re: [CMake] Running OSX Bundle via open after creation with CMake/CPack

2014-06-23 Thread Lucas Soltic
Le 23 juin 2014 à 03:11, Scott Klum scott.k...@gmail.com a écrit : I'm trying to make an OSX bundle using CMake/CPack on OSX that involves OpenCV and Qt (although I don't think those dependencies matter at this point). Everything compiles and the bundle is created fine, and I have a

[CMake] Creating a relocatable ProjectConfig.cmake when build uses absolute paths

2018-01-10 Thread Lucas Soltic
Hello, I'm trying to create a relocatable package configuration file but I'm having a hard time with absolute paths that are used during the build. Note that I use CMake 3.10.0. First of all for the include path I'm using this: target_include_directories(MyStaticTarget PUBLIC

Re: [CMake] Recommandation for macOS framework install rules

2018-01-19 Thread Lucas Soltic
Hello, Should I conclude that there are no recommendations? Best regards, Lucas > Le 17 janv. 2018 à 23:49, Lucas Soltic <lucas.sol...@orange.fr> a écrit : > > Hello, > > By default library install() command uses CMAKE_INSTALL_PREFIX (/usr/local by > default) as a b

Re: [CMake] Recommandation for macOS framework install rules

2018-01-22 Thread Lucas Soltic
ost usual thing is for your code to be self-contained in your > .app bundle. Perhaps if you described more what kind of thing you are > building and why you don't want to do the usual thing, people will have more > advice... > > > On Fri, 19 Jan 2018 19:44:03 +0100, Lucas S

[CMake] Recommandation for macOS framework install rules

2018-01-17 Thread Lucas Soltic
Hello, By default library install() command uses CMAKE_INSTALL_PREFIX (/usr/local by default) as a base for relative install paths. But when you define install rules for macOS frameworks, it doesn't make much sense to install them there. I'd rather expect something like /Library/Frameworks.

Re: [CMake] Recommandation for macOS framework install rules

2018-01-22 Thread Lucas Soltic
> Le 19 janv. 2018 à 20:01, J Decker <d3c...@gmail.com> a écrit : > > > >> On Fri, Jan 19, 2018 at 10:44 AM, Lucas Soltic <lucas.sol...@orange.fr> >> wrote: >> Hello, >> Should I conclude that there are no recommendations? >> > I

Re: [CMake] Swift executables with MACOSX_BUNDLE fail to find libswiftCore.dylib

2018-03-06 Thread Lucas Soltic
If full support for Swift was added to CMake yes why not. But I’m not a CMake developer and considering current Swift support it’s a bit early I think. I mean Swift support should come as a global feature, not just this specific point. > Le 6 mars 2018 à 11:02, Harry Mallon