Re: [CMake] Proper options with cmake

2013-06-24 Thread Rolf Eike Beer
Gennadiy Rozental wrote: > Hi, > > How do I implement a proper option with default value. Both boolean and > string. > > If I define option like this: > > option( GOO "descr" OFF ) > > here is what happends: > > 1. First time I run cmake without specifying GOO, GOO is OFF > 2. Any time I run c

Re: [CMake] how to write the following comand into cmake file.

2013-06-24 Thread 丁老师
thanks. but how to use it. how to install it into cmake. 在 2013-06-25 00:16:01,"Jed Brown" 写道: >丁老师 writes: > >> I develop a parallel code with PETSc, it can sucessfully compiled with >> the following mpic++ command, but how to translate it into a cmake >> file. so i can further develop i

Re: [CMake] how to write the following comand into cmake file.

2013-06-24 Thread Jed Brown
丁老师 writes: > thanks. but how to use it. how to install it into cmake. Like all Find*.cmake modules. It follows the usual conventions. > 在 2013-06-25 00:16:01,"Jed Brown" 写道: >>丁老师 writes: >> >>> I develop a parallel code with PETSc, it can sucessfully compiled with >>> the following mpic++

Re: [CMake] how to write the following comand into cmake file.

2013-06-24 Thread Yonggang Luo
OK, gotcha, After trying out a recent build of Kdevelop4, I decided to give CMake a go. I currently have a project running utilizing MPI (parallellization libraries). This is nice and not that hard to use, but the linking of the project gets arbitrarily complicated. What helped me before when usin

Re: [CMake] how to write the following comand into cmake file.

2013-06-24 Thread Yonggang Luo
I don't know what do you want to do? It's seems mpic++ didn't support by mpic++. 2013/6/24 丁老师 : > I develop a parallel code with PETSc, it can sucessfully compiled with the > following mpic++ command, but how to translate it into a cmake file. so i > can further develop it in kdevelop 4.4. > > mp

[CMake] CMAKE_BUILD_TYPE case sensitivity

2013-06-24 Thread Anil Gunturu
Is the CMAKE_BUILD_TYPE case sensitive. I have seen references to both "Debug" and "DEBUG" in the mailing lists. Thanks, -Anil -- 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 check the

Re: [CMake] Something amiss from RPATH

2013-06-24 Thread Vittorio Giovara
On Mon, Jun 17, 2013 at 8:59 PM, Alexander Neundorf wrote: > On Tuesday 11 June 2013, Vittorio Giovara wrote: > > Hi, > > I've been following the guide > > http://www.cmake.org/Wiki/CMake_RPATH_handlingfor using my libraries > > with my executable on Unix, but even with any > > combination of the

Re: [CMake] INSTALL_NAME_DIR ignored in add_library?

2013-06-24 Thread Vittorio Giovara
On Thu, Jun 13, 2013 at 4:54 PM, Clinton Stimpson wrote: > The INSTALL_NAME_DIR property applies at install time. If you want it to > apply at build time, where it would show up on the link line, you need to > set > BUILD_WITH_INSTALL_RPATH. > > I found the issues, CMAKE_INSTALL_NAME_DIR got igno

[CMake] Strange escaping of cache variables

2013-06-24 Thread Julien Bigot
Hi, I'm trying to make a module to find out how to "stringify" a symbol in Fortran preprocessing. With most compiler you would write #SYMBOL as in C, but with gfortran, you have to use 'SYMBOL' (but it between single quotes) I've written a module that uses try_run (bad for cross compiling but I

[CMake] how to write the following comand into cmake file.

2013-06-24 Thread 丁老师
I develop a parallel code with PETSc, it can sucessfully compiled with the following mpic++ command, but how to translate it into a cmake file. so i can further develop it in kdevelop 4.4. mpic++ main.cpp -o main -I/home/ztdep/Downloads/petsc-3.3-p6/inc… -I/home/ztdep/Downloads/petsc-3.3-p6/arc

Re: [CMake] CMAKE set linker variables (including custom linker script)

2013-06-24 Thread Vittorio Giovara
On Thu, Jun 20, 2013 at 9:57 PM, Martin Osterloh < martin.oster...@dartmouth.edu> wrote: > I am currently migrating my project to CMAKE and so far it has been > going quite well. I am using the standard “ld” as a linker with options –N > –S –q –T > > ** ** > > In my CMakeLists.txt I do: