[CMake] How to install files produced by custom targets

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 will

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

Hi Lucas, you could look into install(CODE ...) or its escaping-hell-avoiding brother, install(SCRIPT ...). The code/script could then be something like execute_process(COMMAND make install ...) or perhaps even execute_process(COMMAND ${CMAKE_BUILD_TOOL} install ...). Petr On Fri, Sep 6, 2013 a

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

I just wanted to point out the existence of CMAKE_BUILD_TOOL, as it's related. In your case, however, you're probably better off hardcoding 'make'. It should actually be done the same way you run 'make' in your custom command creating the library. On Fri, Sep 6, 2013 at 2:08 PM, Lucas Soltic wro

Re: [CMake] CMAKE__OUTPUT_EXTENSION

On Thu, Sep 5, 2013 at 8:22 AM, Michael Wild wrote: > [snip long rant] > Sorry, Alex. If had scrolled down a bit more in CMakeInformation.cmake, I would have seen the hook variables CMAKE_USER_MAKE_RULES_OVERRIDE{,_}. However, can I request that this be documented? Michael -- Powered by www.k

[CMake] cross-compilation bug with swig

Hi, There is an 1 year old unresolved bug (with patch!) with the detection of swig related to cross-compiling. The original bug report is here: http://www.cmake.org/Bug/view.php?id=13449 I filed the same bug report recently here by mistake: http://www.cmake.org/Bug/view.php?id=14359, I guess i

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

Woops wrong target email. So just so that anyone can read.. here it is: Début du message réexpédié : > De : Lucas Soltic > Objet : Rép : [CMake] How to install files produced by custom targets > Date : 6 septembre 2013 19:15:27 UTC+02:00 > À : Petr Kmoch > > Le 6 sept. 2013 à 14:23, Petr Kmoch

Re: [CMake] CMAKE__OUTPUT_EXTENSION

Both CMAKE_USER_MAKE_RULES_OVERRIDE{,_} are both documented: http://cmake.org/cmake/help/v2.8.11/cmake.html#variable:CMAKE_USER_MAKE_RULES_OVERRIDE http://cmake.org/cmake/help/v2.8.11/cmake.html#variable:CMAKE_USER_MAKE_RULES_OVERRIDE_LANG If the documentation isn't sufficient, can you please sug

[CMake] [RFC] cmake analog to AC_SEARCH_LIBS

Hi, all. I'm using this macro to get AC_SEARCH_LIBS (from GNU autoconf) functionality with CMake. First of all, this macro searhes the function on libc, then, if not found, in the given libraries. It sets two variables: 1) boolean if function found 2) string - in which library (may be empty). I

Re: [CMake] Confusion with include() relativity

If this is indeed the case I think the behavior should be modified to respect CMAKE_CURRENT_LIST_DIR. Because, the parent include() command hasn't completed until the nested include() commands have completed, and I think it's a huge limitation that nested include() commands are still referencing th

Re: [CMake] CMAKE__OUTPUT_EXTENSION

It would be useful if these variables were mentioned in the documentation for CMAKE__OUTPUT_EXTENSION. Otherwise this is hardly discoverable. Michael On 06.09.2013 21:28, Robert Maynard wrote: > Both CMAKE_USER_MAKE_RULES_OVERRIDE{,_} are both documented: > > http://cmake.org/cmake/help/v2.8.11