Re: [CMake] link errors using OpenMP

At least for gcc I think you can fix this by passing "${OpenMP_CXX_FLAGS}" to the linker as well (e.g. LINKER_FLAGS target property). -fopenmp at the link stage will instruct gcc to pass the appropriate libraries to the linker. Nils On 10/08/2012 11:30 PM, Matthew Woehlke wrote: When I write

Re: [CMake] setting LINKER_LANGUAGE still adds -lstdc++

On Tue, Oct 9, 2012 at 12:07 AM, Eric Noulard wrote: > 2012/10/9 James Bigler : > > In my project I need to manually link against a special version of > > libstdc++, so I manually set the target link language to C and then add > my > > special library to the link line. On Linux this seems to work

[CMake] adding headers for QTCreator

Hi, I try to add all header files in the include directory so they are visible in QTCreator. My attempt looks like this. file(GLOB Demo_HEADERS RELATIVE ${CMAKE_SOURCE_DIR}/include "*.h") message(STATUS "") message(STATUS "${Demo_HEADERS}") message(

Re: [CMake] adding headers for QTCreator

Hi Witold. Using RELATIVE does not change where the files are looked for, only how they are reported. I believe you need this: file(GLOB Demo_HEADERS RELATIVE ${CMAKE_SOURCE_DIR}/include "include/*.h") Hope this help. Petr On Tue, Oct 9, 2012 at 9:34 AM, Witold E Wolski wrote: > Hi, > > I tr

Re: [CMake] setting LINKER_LANGUAGE still adds -lstdc++

2012/10/9 James Bigler : > On Tue, Oct 9, 2012 at 12:07 AM, Eric Noulard > wrote: >> >> 2012/10/9 James Bigler : >> > In my project I need to manually link against a special version of >> > libstdc++, so I manually set the target link language to C and then add >> > my >> > special library to the

Re: [CMake] New wiki page "CMake Live Cycle Considerations"

Thanks for the roses, Alex ;-) On Monday, 8. October 2012, 20:24:32, Alexander Neundorf wrote: > Hi, > > I just found this new page in the cmake wiki and I think this is very > useful information: > http://www.cmake.org/Wiki/CMake_Live_Cycle_Considerations > > Please help keeping it up-to-date >

[CMake] Need cmake to work on AIX 5.3

Hi, I have to get a build of my product on AIX 5.3 (powerpc) because of backward compatibility concerns. The product builds fine on such a system using conventional gmake. However, cmake fails to identify the xlc/xlC compilers correctly and reports them as broken. What is the way to fix this? Cou

Re: [CMake] Need cmake to work on AIX 5.3

Hi Arindam, Maybe you can try this way: http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_use_a_different_compiler.3F Xavier On Tue, Oct 9, 2012 at 11:58 AM, Arindam Mukherjee < arindam.muker...@gmail.com> wrote: > Hi, > > I have to get a build of my product on AIX 5.3 (powerpc) because of > backw

Re: [CMake] New wiki page "CMake Live Cycle Considerations"

On 8 October 2012 19:24, Alexander Neundorf wrote: > Hi, > > I just found this new page in the cmake wiki and I think this is very useful > information: > http://www.cmake.org/Wiki/CMake_Live_Cycle_Considerations Looks great. I was looking for something like this recently. However, shouldn't it b

Re: [CMake] New wiki page "CMake Live Cycle Considerations"

On Tuesday, 9. October 2012, 12:25:51, Matt Williams wrote: > On 8 October 2012 19:24, Alexander Neundorf wrote: > > Hi, > > > > I just found this new page in the cmake wiki and I think this is very > > useful information: > > http://www.cmake.org/Wiki/CMake_Live_Cycle_Considerations > > Looks g

Re: [CMake] [cmake-developers] setting LINKER_LANGUAGE still adds -lstdc++

On 10/09/2012 01:59 AM, James Bigler wrote: > On Mon, Oct 8, 2012 at 10:40 PM, James Bigler > wrote: > In my project I need to manually link against a special version of libstdc++ > add_library(a SHARED a.cpp) > set_target_properties(a PROPERTIES LINKER_LANGUA

[CMake] Question about find package in Module mode

Hello, I am using find_package in Module mode for a Library that is also build using cmake. The Library is build in a way that it can be used both from the build dir, and from the installed location. When using find_package it always seems to prefer the build dir version, which is somewhat s

Re: [CMake] Question about find package in Module mode

Hi, On Tue, Oct 9, 2012 at 3:46 PM, Fabio Fracassi wrote: > Hello, > > I am using find_package in Module mode for a Library that is also build > using cmake. > The Library is build in a way that it can be used both from the build dir, > and from the installed location. > > When using find_package

Re: [CMake] Question about find package in Module mode

On 10/9/12 5:05 PM, Andreas Pakulat wrote: Hi, On Tue, Oct 9, 2012 at 4:42 PM, Fabio Fracassi wrote: On 10/9/12 4:12 PM, Andreas Pakulat wrote: Hi, On Tue, Oct 9, 2012 at 3:46 PM, Fabio Fracassi wrote: Hello, I am using find_package in Module mode for a Library that is also build using cm

Re: [CMake] Need cmake to work on AIX 5.3

On 10/9/2012 5:58 AM, Arindam Mukherjee wrote: Hi, I have to get a build of my product on AIX 5.3 (powerpc) because of backward compatibility concerns. The product builds fine on such a system using conventional gmake. However, cmake fails to identify the xlc/xlC compilers correctly and reports

Re: [CMake] Need cmake to work on AIX 5.3

On Tue, Oct 9, 2012 at 9:21 PM, Bill Hoffman wrote: > On 10/9/2012 5:58 AM, Arindam Mukherjee wrote: >> >> Hi, >> >> I have to get a build of my product on AIX 5.3 (powerpc) because of >> backward compatibility concerns. The product builds fine on such a >> system using conventional gmake. However

Re: [CMake] Need cmake to work on AIX 5.3

On 10/9/2012 3:06 PM, Arindam Mukherjee wrote: On Tue, Oct 9, 2012 at 9:21 PM, Bill Hoffman wrote: On 10/9/2012 5:58 AM, Arindam Mukherjee wrote: Hi, I have to get a build of my product on AIX 5.3 (powerpc) because of backward compatibility concerns. The product builds fine on such a system

Re: [CMake] Question about find package in Module mode

Hi, On Tue, Oct 9, 2012 at 5:39 PM, Fabio Fracassi wrote: > On 10/9/12 5:05 PM, Andreas Pakulat wrote: > On Tue, Oct 9, 2012 at 4:42 PM, Fabio Fracassi > What do you mean with "package registry" here? > > It means the package registry where cmake stores previously build packages, > which can be d