[CMake] CDash Dynamic Analysis

Hi I'm trying to integrate custom tools to CDash Dynamic analysis. I'm not that certain on what is the way I should be going. Is there a way to tell cmake to pick up lines from a program as defects in the custom tool submission xml? Do i need to make a program that generates a valid xml file?

Re: [CMake] add_definition??

On 04/13/2011 11:50 PM, klaas.holwerda wrote: > Hi, > > I use ADD_DEFINITIONS( ${wxWidgets_DEFINITIONS} ) to add flags for > compilation like this: > > set( wxWidgets_CXX_FLAGS ${wxWidgets_CXX_FLAGS} > -D__WXMSW__ -D__GNUWIN32__ -D__WIN95__ > -fexceptions -fno-pcc-struct-retur

Re: [CMake] DESTDIR behaviour with different variable name

On 04/12/2011 04:36 PM, Tomasz Grobelny wrote: > On Tue, 12 Apr 2011 03:44:04 +0200, Michael Hertling > wrote: >> On 04/11/2011 10:42 PM, Tomasz Grobelny wrote: >>> On Monday 11 April 2011 21:55:48 Alexander Neundorf wrote: On Monday 11 April 2011, Tomasz Grobelny wrote: > On Mon, 11 Apr

Re: [CMake] embedded path in shared library linked into another shared library

On 04/13/2011 08:52 PM, Alexander Neundorf wrote: > On Tuesday 12 April 2011, Michael Hertling wrote: >> On 04/11/2011 11:10 PM, David Aiken wrote: >>> That didn't work for me.. I've got it simplified down to: >>> SET(CMAKE_SKIP_RPATH TRUE) >>> and in the CMakeCache.txt I see: >>> CMAKE_SKIP_RPATH:

[CMake] add_definition??

Hi, I use ADD_DEFINITIONS( ${wxWidgets_DEFINITIONS} ) to add flags for compilation like this: set( wxWidgets_CXX_FLAGS ${wxWidgets_CXX_FLAGS} -D__WXMSW__ -D__GNUWIN32__ -D__WIN95__ -fexceptions -fno-pcc-struct-return -fstrict-aliasing -Wall#all warnings

Re: [CMake] Finding dynamic libraries with major interface revision numbers (2)

Thanks Michael Doing the following ends up working ... IF(UNIX) # If the faster 'gold' linker is used, to avoid complaints about undefined symbol # '_gfortran_concat_string', '_gfortran_pow_i4_i4', ... , let's link against gfortran libraries. # These errors happen while linking against VTK

Re: [CMake] Finding dynamic libraries with major interface revision numbers (2)

Yes it does ... see below Does that mean I specified something incorrectly within my project ? Note also that the problem occurs only when VTK is built statically ... Jc readelf -d /home/jchris/Projects/R-2.11.1/lib64/R/lib/libR.so |grep NEEDED 0x0001 (NEEDED) Shared li

Re: [CMake] Finding dynamic libraries with major interface revision numbers (2)

On 04/13/2011 09:26 PM, Brad King wrote: > On 04/13/2011 02:44 PM, Jean-Christophe Fillion-Robin wrote: >> Is there a solution to find a library having a revision number ? > > You can specify the actual library file name "libgfortran.so.3". AFAIK, this is not sufficient because FIND_LIBRARY() onl

Re: [CMake] Finding dynamic libraries with major interface revision numbers (2)

On 04/13/2011 03:37 PM, Jean-Christophe Fillion-Robin wrote: > 1) I have a project XYZ that linked against VTK static which also linked > GnuR shared [snip] > /usr/bin/ld: /home/jchris/Projects/R-2.11.1/lib64/R/lib/libRlapack.so: > error: undefined reference to '_gfortran_concat_string' Doesn't Gn

Re: [CMake] Finding dynamic libraries with major interface revision numbers (2)

On Wed, Apr 13, 2011 at 3:26 PM, Brad King wrote: > On 04/13/2011 02:44 PM, Jean-Christophe Fillion-Robin wrote: > > Is there a solution to find a library having a revision number ? > > You can specify the actual library file name "libgfortran.so.3". > Great > > However, you shouldn't need to fi

Re: [CMake] Finding dynamic libraries with major interface revision numbers (2)

On 04/13/2011 02:44 PM, Jean-Christophe Fillion-Robin wrote: > Is there a solution to find a library having a revision number ? You can specify the actual library file name "libgfortran.so.3". However, you shouldn't need to find implicit compiler runtime libraries. Are you trying to mix C++ and F

Re: [CMake] embedded path in shared library linked into another shared library

On Tuesday 12 April 2011, Michael Hertling wrote: > On 04/11/2011 11:10 PM, David Aiken wrote: > > That didn't work for me.. I've got it simplified down to: > > SET(CMAKE_SKIP_RPATH TRUE) > > and in the CMakeCache.txt I see: > > CMAKE_SKIP_RPATH:BOOL=NO > > That's not surprising as your SET() comma

[CMake] Finding dynamic libraries with major interface revision numbers (2)

Hi Folks, Is there a solution to find a library having a revision number ? For example, on Ubuntu, after I installed 'libgfortran3', there is the library /usr/lib/libgfortran.so.3 then the following command failed: FIND_LIBRARY(GFortran_LIBRARY gfortran) If I create the symlink /usr/lib/libgf

Re: [CMake] Fwd: Adding custom directories to PATH enviroment

On 04/13/2011 05:52 PM, Gabriele Greco wrote: > Then you haven't read or understood my message ;-) Instead of calling > idlcc directly in the add_custom_command, you call a wrapper script, > that sets the PATH environment variable, and *then* invokes idlcc. > > > Ok, I implemented you

Re: [CMake] Fwd: Adding custom directories to PATH enviroment

> > Then you haven't read or understood my message ;-) Instead of calling > idlcc directly in the add_custom_command, you call a wrapper script, > that sets the PATH environment variable, and *then* invokes idlcc. > Ok, I implemented your solution and it works, thanks! One additional comment: Cre

Re: [CMake] Confusing problem with building VTK via external project

Strange as it may seem, there must have been something fracked up in my Emacs environment because this craziness went away when I restarted Emacs. Though the particulars of how this began are mysterious. On Wed, Apr 13, 2011 at 10:26 AM, David Cole wrote: > On Wed, Apr 13, 2011 at 11:04 AM, kent

Re: [CMake] Confusing problem with building VTK via external project

On Wed, Apr 13, 2011 at 11:04 AM, kent williams wrote: > I've all of a sudden started having trouble building VTK via an > ExternalProject. OS X, CMake 2.8.4, Standard GCC 4.2 compilers, stock > VTK 5.6.1. > > output of make VERBOSE=1 of the top-level project, you can see that > QT_QMAKE_EXECUTAB

[CMake] Confusing problem with building VTK via external project

I've all of a sudden started having trouble building VTK via an ExternalProject. OS X, CMake 2.8.4, Standard GCC 4.2 compilers, stock VTK 5.6.1. output of make VERBOSE=1 of the top-level project, you can see that QT_QMAKE_EXECUTABLE is set, but when CMake runs, it somehow ignores the variables se

Re: [CMake] Searchable mail archive

J.S. van Bethlehem wrote: > Dear CMake users, > > This week I started to investigate possibilities to move my build-system > over to CMake after hearing a lot of good stories about it. To be > honest, so far I'm still not quite convinced. The learning (I find at > least) is rather steep and the d

Re: [CMake] Fwd: Adding custom directories to PATH enviroment

On 04/13/2011 01:04 PM, Gabriele Greco wrote: > > > > And then configure and run it like this: > > CMakeLists.txt: > --- > # ... > configure_file(foo_wrapper.cmake.in >"${CMAKE_CURRENT_BINARY_DIR}/foo_wrapper.cmake" @ONLY) >

[CMake] Fwd: Adding custom directories to PATH enviroment

> And then configure and run it like this: > > CMakeLists.txt: > --- > # ... > configure_file(foo_wrapper.cmake.in >"${CMAKE_CURRENT_BINARY_DIR}/foo_wrapper.cmake" @ONLY) > add_custom_command(OUTPUT bar > COMMAND "${CMAKE_COMMAND}" -P >"${CMAKE_CURRENT_BINARY_DIR}/foo_wrapper.c

Re: [CMake] Adding custom directories to PATH enviroment

On 04/13/2011 11:51 AM, Gabriele Greco wrote: > Hi, > > I've started using cmake on my projects since a few weeks so I'm still a > beginner. > > The system works very well I only have a problem. > > I need to have a directory inside the project tree included in the > command search path (the en

[CMake] Adding custom directories to PATH enviroment

Hi, I've started using cmake on my projects since a few weeks so I'm still a beginner. The system works very well I only have a problem. I need to have a directory inside the project tree included in the command search path (the enviroment variable PATH). I tried with: set(ENV{PATH} "${PROJECT

[CMake] Resource file skipped without warning

Hello everybody, I am using CMake 2.8 to build a Fortran executable that uses Winteracter graphical library. The build is performed using Intel Fortran Compiler. I read in previous discussion (http://www.cmake.org/pipermail/cmake/2004-January/004664.html) that just adding the rc file as a sou

Re: [CMake] Searchable mail archive

2011/4/13 Michael Wild : > On 04/13/2011 09:45 AM, J.S. van Bethlehem wrote: >> Dear CMake users, >> >> This week I started to investigate possibilities to move my build-system >> over to CMake after hearing a lot of good stories about it. To be >> honest, so far I'm still not quite convinced. The

[CMake] How to run CMake generated projects in VS2008

hi all, I want to know which is the proper way of generating/using the CMake generated VS2008 project files. I've downloaded the OpenGL samples pack from G-TRUC.NET. In order to not hassle with include files, dependencies etcc.. from forums I've been instructed to use the CMake to generate

Re: [CMake] Searchable mail archive

On 04/13/2011 09:45 AM, J.S. van Bethlehem wrote: > Dear CMake users, > > This week I started to investigate possibilities to move my build-system > over to CMake after hearing a lot of good stories about it. To be > honest, so far I'm still not quite convinced. The learning (I find at > least) is

[CMake] Searchable mail archive

Dear CMake users, This week I started to investigate possibilities to move my build-system over to CMake after hearing a lot of good stories about it. To be honest, so far I'm still not quite convinced. The learning (I find at least) is rather steep and the documentation rather sparse (afaics)

Re: [CMake] Properly Detecting Win64

>> Maybe you can base the package name by testing the generator name. > > I need to do that to e.g. get a useful build naming in CTest scripts. At > that point CMAKE_SIZEOF_VOID_P is not available anyway. And I think that > using this is just a bad idea. How do you decide if it's IA64 or AMD64? [.

Re: [CMake] Properly Detecting Win64

> Maybe you can base the package name by testing the generator name. I need to do that to e.g. get a useful build naming in CTest scripts. At that point CMAKE_SIZEOF_VOID_P is not available anyway. And I think that using this is just a bad idea. How do you decide if it's IA64 or AMD64? I use this