Re: [CMake] Using C++ compilers for C source files?

Hi, Look at that thread... http://www.cmake.org/pipermail/cmake/2009-March/028352.html Regards, Alexandre -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Blake Sent: Friday, 03 April 2009 16:46 To: cmake@cmake.org Subject: [CMake] Us

Re: [CMake] Output directory for genereated ui_Header.h files

Hi, I wrote this macro to generate my ui.[ch] and moc files in my source directory. Use it as a QT4_WRAP_UI replacement. The macro also creates a "ui" target which generates all these files. (Note: I use it with Qt 3, and did not check if uic is used the same way on Qt 4. #

Re: [CMake] Compile all .c source files with the CXX compiler

hem has no effect. So, should these CMAKE__SOURCE_FILE_EXTENSIONS variables be considerered as read-only? Is this a bug? -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Pau Garcia i Quiles Sent: Tuesday, 31 March 2009 17:21 To: Alexandre Feblot

[CMake] Compile all .c source files with the CXX compiler

Hi, In my project, all sources named .c are C++ files, and should be considered as CXX language files. I tried to set this with CMAKE__SOURCE_FILE_EXTENSIONS, at the very beginning of my project, without success. How should I do it? cmake_minimum_required (VERSION 2.6) project(MY_PROJ

Re: [CMake] How to surround an imported lib with extra flags onlink?

If you find a solution to this, please let me know. Best Regards Martin Alexandre Feblot wrote: > > Hi again, > > Would anybody have a solution for this? > > Thanks > > Alexandre > > > > *

Re: [CMake] How to surround an imported lib with extra flags on link?

Hi again, Would anybody have a solution for this? Thanks Alexandre Sent: Monday, 30 March 2009 17:31 Hi, I import some libs like this: add_library(${name} ${type} IMPORTED) set_target_properties(${name} PROPERTIES IMPO

[CMake] How to surround an imported lib with extra flags on link?

Hi, I import some libs like this: add_library(${name} ${type} IMPORTED) set_target_properties(${name} PROPERTIES IMPORTED_LINK_INTERFACE_LIBRARIES "${other_imported_libs}" IMPORTED_LOCATION "${file}" ) At the end, I link an executable

Re: [CMake] Feature request: generic (config-like) selector on target_link_libraries

> > Specifying the lib4 dependency in the exe? But what about dependencies > > order in the link line? In my example, lib4-A or lib4-B must appear > > after lib3, if I want lib4 symbols required by lib3 to be added. In your > > solution, lib4 might as well be added by cmake just after lib1 and > >

Re: [CMake] Feature request: generic (config-like) selector on target_link_libraries

, the same lib3 must then depend on lib4-B. Regards, Alexandre -Original Message- From: Michael Wild [mailto:them...@gmail.com] Sent: Tuesday, 24 March 2009 13:43 To: Alexandre Feblot Cc: Cmake Mailing List Subject: Re: [CMake] Feature request: generic (config-like) selector on target_li

[CMake] Feature request: generic (config-like) selector on target_link_libraries

Hi, I'm facing an issue while trying to port my current build system to cmake, and it seems there is no way to solve it currently. At least, nobody in the mailing list found one. The only suggestion was to totally recode the dependency mechanism with macros instead of relying on the Cmake stand

Re: [CMake] How to describe lib dependencies when a lib has different possible implementations?

33 PM, Alexandre Feblot wrote: > Hum, > I don't see what you mean. In the cmake spirit, my executable don't > even know they will depend on lib4. exe1 just knows it depends on > lib1. Then lib1 just knows it depends on lib3. Then, lib3 just knows > it depends on lib

Re: [CMake] How to describe lib dependencies when a lib has different possible implementations?

eudi 19 mars 2009 19:04 À : Alexandre Feblot Cc : cmake@cmake.org Objet : Re: [CMake] How to describe lib dependencies when a lib has different possible implementations? If you want to compile two execs, one for each static library you can use a two element list and go "for_each" over

Re: [CMake] How to describe lib dependencies when a lib has different possible implementations?

no idea what you would put in those ifs. Chris. Alexandre Feblot wrote: > Hi, > > I'm facing an issue while trying to port my current build system to > cmake and don't know is there is a way to solve it: > > In our project, we build a bunch of *static* libs (about 3

[CMake] How to describe lib dependencies when a lib has different possible implementations?

Hi, I'm facing an issue while trying to port my current build system to cmake and don't know is there is a way to solve it: In our project, we build a bunch of static libs (about 360) and several executables on them. * one library, in the middle of the lib dependency chain, has in fact 2 diff

Re: [CMake] Pparallel build on multiple directories?

Ok Bill, thanks for that detailled info. It will be really useful. Regards, Alexandre -Original Message- From: Bill Hoffman [mailto:bill.hoff...@kitware.com] Sent: Thursday, 15 January 2009 17:23 To: Alexandre Feblot Cc: cmake@cmake.org Subject: Re: [CMake] Pparallel build on multiple

Re: [CMake] Define a library target without using the add_librarycommand ? => Working with repositories => IMPORTED targets

make.org] On Behalf Of Andreas Pakulat Sent: Monday, 12 January 2009 14:38 To: cmake@cmake.org Subject: Re: [CMake] Define a library target without using the add_librarycommand ? <==> Working with repositories On 12.01.09 11:27:29, Alexandre Feblot wrote: > Is there a way to define

Re: [CMake] Pparallel build on multiple directories?

nstall once and share between multiple servers. I might give it a try though, just to see if I can have it working here... Thanks for the suggestion. Regards, Alexandre -Original Message- From: Bill Hoffman [mailto:bill.hoff...@kitware.com] Sent: Monday, 12 January 2009 20:24 To: Alex

Re: [CMake] add_library and target_link_libraries in differentdirectories?

OK, thanks for the explanation. It's rather clear now that this is probably not the way to go for me. Exported targets might be a solution... Regards, Alexandre -- A computer scientist is someone who fixes things that aren't broken. -Original Message- From: cmake-boun...@cmake.org [mai

Re: [CMake] Pparallel build on multiple directories?

[mailto:bill.hoff...@kitware.com] Sent: Monday, 12 January 2009 17:28 To: Alexandre Feblot Cc: cmake@cmake.org Subject: Re: [CMake] Pparallel build on multiple directories? Alexandre Feblot wrote: > Ugh! > > > > I'm using exactly the same (cmake 2.6.2, linux, unix makefiles), a

Re: [CMake] add_library and target_link_libraries indifferentdirectories?

where else. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of David Cole Sent: Monday, 12 January 2009 16:05 To: Alexandre Feblot Cc: cmake@cmake.org Subject: Re: [CMake] add_library and target_link_libraries indifferentdirectories? R

Re: [CMake] add_library and target_link_libraries in differentdirectories?

as Pakulat Sent: Monday, 12 January 2009 14:32 To: cmake@cmake.org Subject: Re: [CMake] add_library and target_link_libraries in differentdirectories? On 12.01.09 11:27:28, Alexandre Feblot wrote: > Hi, > > > > I have not been able to define a library dependency in a director

Re: [CMake] Pparallel build on multiple directories?

Sent: Monday, 12 January 2009 13:56 To: Alexandre Feblot Subject: Re: [CMake] Pparallel build on multiple directories? 2009/1/12 Alexandre Feblot : > Hi, > I try to figure out cmake parallel build capabilities. > > As far as I see, multiple files in a directory ca

[CMake] Define a library target without using the add_library command ? <==> Working with repositories

Hi, Is there a way to define a library target, on which I could use target_link_libraries(), without creating/building this library, i.e. without defining it with add_library(), but with add_custom_target for instance ? The goal is to work on a small part of a large project: I'd like to hav

[CMake] add_library and target_link_libraries in different directories?

Hi, I have not been able to define a library dependency in a directory different from the one in which the library target is created. Is this done by design, or is there any way to do it? My goal would be to have - each library in it's own directory (and a CMakeLists.txt file wit

[CMake] Pparallel build on multiple directories?

Hi, I try to figure out cmake parallel build capabilities. As far as I see, multiple files in a directory can be processed in parallel, but multiple subdirectories of a single cmake project are still processed one after the other. Can someone confirm this behaviour? Or can I do better?