[CMake] make target export file follow symlinks (or something better?)

2014-08-22 Thread Nico Schlömer
Hi all, I'm linking my shared library against ``` /usr/lib/x86_64-linux-gnu/libhdf5.so -> libhdf5.so.7.0.0 /usr/lib/x86_64-linux-gnu/libhdf5.so.7 -> libhdf5.so.7.0.0 /usr/lib/x86_64-linux-gnu/libhdf5.so.7.0.0 ``` resulting in the dynamic dependency ``` $ ldd mylib.so.1.0.0 | grep hdf5 libhdf5.so.

[CMake] CMake Error With No Description

2014-08-22 Thread David Zemon
Hello all, I have a working (in Linux) CMake project and am now trying to make it cross-platform. I'm nearly there! CMake generates the Makefiles without error but upon trying to run Make, things die. Here's the output from "make VERBOSE=1" C:\Users\David\Documents\GitHub\PropWare>make VERBO

Re: [CMake] add_custom_command and CONFIG-dependent output

2014-08-22 Thread David Cole via CMake
Use "${CMAKE_CFG_INTDIR}" in the context of add_custom_command OUTPUT, not $. You may also use that in the COMMAND arguments. See documentation here: http://www.cmake.org/cmake/help/v3.0/variable/CMAKE_CFG_INTDIR.html The $<> generator expressions are relatively new, and do not work in all conte

[CMake] add_custom_command and CONFIG-dependent output

2014-08-22 Thread Braden McDaniel
I'm trying to do this: set(LIB_STAGEDIR "${STAGEDIR}/lib/$") add_custom_command( OUTPUT ${LIB_STAGEDIR} COMMAND ${CMAKE_COMMAND} -E make_directory ${LIB_STAGEDIR} ) …and CMake complains thusly: add_custom_command called with OUTPUT containing a "<". This characte

Re: [CMake] add_custom_command doesn't know about target; but get_target_property does

2014-08-22 Thread Nils Gladitz
On 22.08.2014 18:18, Braden McDaniel wrote: Actually, upon closer inspection, it looks like this doesn't work because $ won't be aware of the current configuration at CMake configure-time. I'm trying to get the configuration-dependent path of the emitted library. (And I need to support Wind

Re: [CMake] add_custom_command doesn't know about target; but get_target_property does

2014-08-22 Thread Braden McDaniel
Nils Gladitz writes: > Perhaps something like: > > file(GENERATE > OUTPUT "${CMAKE_BINARY_DIR}/${LIB_PATHS}/${EXPORT_TARGET}_$" > CONTENT "$" > ) Actually, upon closer inspection, it looks like this doesn't work because $ won't be aware of the current configuration at CMake configu

Re: [CMake] Preferred way to find Qt5 Plugins with CMake 3.x

2014-08-22 Thread Michael Jackson
To answer my own question, this bit of code gets me started: foreach(plugin ${Qt5Gui_PLUGINS}) get_target_property(_loc ${plugin} LOCATION) message("Core Plugin ${plugin} is at location ${_loc}") endforeach() Now I need to find the debug versions of the library.? http://qt-project.org/doc/qt

[CMake] Preferred way to find Qt5 Plugins with CMake 3.x

2014-08-22 Thread Michael Jackson
I am trying to locate specific plugins from the Qt5 installation. I guess in previous iterations of FindQt4 possibly the "QT_PLUGINS_DIR" may have been defined because I am using this variable in my Qt4 based codes. I am still trying to wade my way through Qt5 so I maybe missing something obviou

Re: [CMake] add_custom_command doesn't know about target; but get_target_property does

2014-08-22 Thread Braden McDaniel
On Fri, 2014-08-22 at 12:37 +0200, Nils Gladitz wrote: > On 22.08.2014 02:15, Braden McDaniel wrote: > > Ah. Bummer. > > > > Well, as you might have guessed, I'm trying to address an issue where > > the LOCATION property of a target (EXPORT_TARGET, in the example above) > > was being used. Is the

Re: [CMake] Behaviour of FindPythonInterp appears suboptimal

2014-08-22 Thread David Cole via CMake
>> I thought using FindPythonInterp would be more portable than >> simply invoking "python" directly (i.e. using $PYTHON_EXECUTABLE). > In case you want the newest version of any Python major, as in your > case, try > find_package(PythonInterp 2 REQUIRED). But you are right, this would > also succ

Re: [CMake] Behaviour of FindPythonInterp appears suboptimal

2014-08-22 Thread Rolf Eike Beer
Roger Leigh wrote: > I thought using FindPythonInterp would be more portable than > simply invoking "python" directly (i.e. using $PYTHON_EXECUTABLE). > However, this does not appear to be the case. I'd be interested to > know if this is intentional or if I'm doing something wrong. > > I've tried

[CMake] Behaviour of FindPythonInterp appears suboptimal

2014-08-22 Thread Roger Leigh
I thought using FindPythonInterp would be more portable than simply invoking "python" directly (i.e. using $PYTHON_EXECUTABLE). However, this does not appear to be the case. I'd be interested to know if this is intentional or if I'm doing something wrong. I've tried using "find_package(PythonInte

Re: [CMake] add_custom_command doesn't know about target; but get_target_property does

2014-08-22 Thread Nils Gladitz
On 22.08.2014 02:15, Braden McDaniel wrote: Ah. Bummer. Well, as you might have guessed, I'm trying to address an issue where the LOCATION property of a target (EXPORT_TARGET, in the example above) was being used. Is there some way I can get this information about the target that doesn't invol

Re: [CMake] Linker error with sub project's static libs

2014-08-22 Thread Marcel Loose
Hi Olaf, See my reply below inline. On 21/08/14 20:19, Olaf Peter wrote: > Hello Marcel, >> Olaf, >> >> Unless your code snippets are incomplete, I'm missing the following >> statement in ./source/eea/ui/CMakeLists.txt >> >> target_link_libraries(eea_ui_lib >> eea_ui_schematic_lib)