Re: [CMake] How do I search for personal libraries?

2013-04-02 Thread Michael Wild
You should find this interesting: http://www.cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file In short: * In project A create a AConfig.cmake file and export your targets * In project B call find_package(A REQUIRED) HTH Michael On Wed, Apr 3, 2013 at 7:44 AM, Saad Khatt

Re: [CMake] CMake extracting tar via execute_process does not allow extraction in subdirectories

2013-04-02 Thread Eric Noulard
2013/4/3 Saad Khattak > That prints the directory in the console: > > Z:/engine/src/mySDK > > But did not extract to it. Note that mySDK exists, and the tar is in the > 'src' folder and I am able to extract in the 'src' folder properly. > Ok this is weird. Which version of CMake are you using?

[CMake] How do I search for personal libraries?

2013-04-02 Thread Saad Khattak
Hi, Suppose I have two personal repositories: A and B. Repository B has a dependency on repository A i.e. repository A builds multiple libraries and repository B builds multiple libraries and executables. I can build 32-bit and 64-bit libraries/executables for both by having a 'build' and 'buildx6

Re: [CMake] CMake extracting tar via execute_process does not allow extraction in subdirectories

2013-04-02 Thread Saad Khattak
That prints the directory in the console: Z:/engine/src/mySDK But did not extract to it. Note that mySDK exists, and the tar is in the 'src' folder and I am able to extract in the 'src' folder properly. - Saad On Tue, Apr 2, 2013 at 1:58 AM, Eric Noulard wrote: > COMMAND ${CMAKE_COMMAND} -E e

Re: [CMake] CMake extracting tar via execute_process does not allow extraction in subdirectories

2013-04-02 Thread Saad Khattak
Hi Eric, I created the folder manually, but it still did not extract to that folder. It appears to only be able to extract to the current folder. It 'is' able to create folders that are in the tar as expected. - Saad On Tue, Apr 2, 2013 at 1:50 AM, Eric Noulard wrote: > > > > 2013/4/2 Saad Kh

Re: [CMake] Link different libraries in different targets

2013-04-02 Thread Matthew Woehlke
On 2013-04-02 12:08, domenico wrote: I'm quite new to CMake, so please forgive me if the question seems obvious. My project has lines like : link_directories(/path/to/libA/) add_library(my_project SHARED my_file.cpp) target_link_libraries(my_project A) I browsed help and googled a few, but I st

[CMake] Redirect output from add_custom_target()

2013-04-02 Thread Robert Dailey
I'd like to redirect stderr to stdout in the command invoked by add_custom_target(). Here is my usage: add_custom_target( ${doc_target_name} DEPENDS ${generated_conf} COMMAND ${doxygen_exe} ${generated_conf} WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}

Re: [CMake] MinGW Link with -l instead of path?

2013-04-02 Thread J Decker
So from the silence, either I described my issue badly, or there isn't a way? >From the script at the end, when generating 'unix makefiles' with a mingw environment, or MingW makefiles, these are the gcc commands (compile .obj) c:/tools/unix/mingw.mangled/bin/gcc.exe -Dtest2_EXPORTS -o CMak

Re: [CMake] Link different libraries in different targets

2013-04-02 Thread Ansis Māliņš
Just add more link_directories commands or put more arguments in the one your have: link_directories("/path/to/libA" "path/to/libB") -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and chec

Re: [CMake] Link different libraries in different targets

2013-04-02 Thread Leif Walsh
A few ideas: Set the targets' LINK_FLAGS separately to specify the linker dirs.  Use target_link_libraries on the file path rather than the lib name.  Make an imported library target for the libs in each dir and then link with those targets. (I'm assuming these are not libs you're building)

[CMake] Link different libraries in different targets

2013-04-02 Thread domenico
Hi there ! I'm quite new to CMake, so please forgive me if the question seems obvious. My project has lines like : link_directories(/path/to/libA/) add_library(my_project SHARED my_file.cpp) target_link_libraries(my_project A) I browsed help and googled a few, but I still wonder how I could set

Re: [CMake] Quick question: CMAKE_CXX_FLAGS vs CMAKE_CXX_COMPILE_FLAGS

2013-04-02 Thread Yngve Inntjore Levinsen
Hi, I believe compile flags are *not* used during linking, while CMAKE_CXX_FLAGS will also be used during linking (if your linker language is C++). I do not know of any other differences, but perhaps an expert wants to correct me.. Cheers, Yngve On 02. april 2013 11:21, Daniel Carrera wrote: > H

Re: [CMake] How to configure Fortran compiler, flags, and so on.

2013-04-02 Thread Daniel Carrera
Thanks! On 2 April 2013 10:46, Yngve Inntjore Levinsen wrote: > Hi, > > If you define variables in your environment before configuring cmake > they will be read by cmake. > > The following environment variables (maybe I forget some) are relevant > for fortran code: > FC = fortran compiler > FFLAG

[CMake] Quick question: CMAKE_CXX_FLAGS vs CMAKE_CXX_COMPILE_FLAGS

2013-04-02 Thread Daniel Carrera
Hi everyone, What is the difference between CMAKE_CXX_COMPILE_FLAGS and CMAKE_CXX_FLAGS? The wiki only mentions CMAKE_CXX_FLAGS and CMAKE_C_FLAGS, and those are clearly used for compiling. But if you Google for CMake examples (e.g with MPI) you will quickly find CMake scripts that have CMAKE_CXX_

Re: [CMake] How to configure Fortran compiler, flags, and so on.

2013-04-02 Thread Yngve Inntjore Levinsen
Hi, If you define variables in your environment before configuring cmake they will be read by cmake. The following environment variables (maybe I forget some) are relevant for fortran code: FC = fortran compiler FFLAGS = fortran flags (added to default flags) LDFLAGS = linker flags (any language)