[CMake] cpack and boost dependencies when building a debian installer

Hello everybody, I would like to use cpack (2.8.7) in order to build a debian installer for a c++ library that has a few dependencies namely: - boost (headers + libraries) - fftw3-3 - eigen3 - hdf5 - tiff I would like to set my cpack file in such a way that the minimum ver

[CMake] question about SET_SOURCE_FILES_PROPERTIES

Dear CMakers, I have a Fortran project to be built on Windows and Linux using ifort compiler. For two of the project files, I need to add specific compiler flag (i.e. /assume:byterecl). To do so, I used the following CMake command: SET_SOURCE_FILES_PROPERTIES(file1.f90 PROPERTIES COMPILE_FLAG

Re: [CMake] 32/64 bit flag - solved

On 12/9/2013 2:34 PM, Eric Noulard wrote: 2013/12/9 pellegrini : Thanks Eric for the hint. I read some time ago some stuffs about the CMAKE_SIZEOF_VOID_P variable but unfortunately, in the present case, the problem is a bit different. It can be for example that on a 64 bit machine, I would

Re: [CMake] 32/64 bit flag

On 12/9/2013 1:26 PM, Eric Noulard wrote: 2013/12/9 pellegrini : Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are different

[CMake] 32/64 bit flag

Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are different depending on the 32 or 64 bit versions. Is there a way to automatically de

[CMake] problem with shortcut CPACK/NSIS

wrong with it it would be great. thanks in advance Eric include (InstallRequiredSystemLibraries) # General CPACK options set(CPACK_PACKAGE_NAME ${PROJECT_NAME}) set(CPACK_PACKAGE_VENDOR "Eric Pellegrini - Institut Laue Langevin") set(CPACK_PACKAGE_VERSION_MAJOR "1") set(CPA

[CMake] cache behaviour

90 -- Checking whether C:/Intel/Composer XE/bin/ia32/ifort.exe supports Fortran 90 -- yes -- Configuring done -- Generating done -- Build files have been written to: C:/Users/pellegrini/work/diffraction/sxtalsoft/build/ifort If a run it a second time WITHOUT deleting the CMakeCache.txt file wi

Re: [CMake] Default value for CMAKE_BUILD_TYPE

izeRel" "RelWithDebInfo") endif() See http://vtk.org/gitweb?p=VTK.git;a=blob;f=CMakeLists.txt;h=a57fd66ef333fc26bf74fe658c88c3c634f54c3a;hb=HEAD#l12 Hth Jc On Fri, May 11, 2012 at 11:21 AM, pellegrini <mailto:pellegr...@ill.fr>> wrote: Hi all, when cmake is

[CMake] Default value for CMAKE_BUILD_TYPE

Hi all, when cmake is run without specifying the build type using -D CMAKE_BUILD_TYPE, it is the Debug mode that is selected as the default. I would like to find a way to use Release as the default value when the user does not specify any build type in the cmake command line. From one of my p

[CMake] avoiding complete rebuild when the user changes

escape from this feature ? thanks a lot see you Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- 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

Re: [CMake] About CMAKE_INSTALL_PREFIX - solved

info/cmake -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- 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 CMake FAQ at: http://www.cmake.org/Wik

[CMake] About CMAKE_INSTALL_PREFIX

rectly the values he provided, and if not so, I take the parent directory of the default value. Is that possible ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other Kitware open-source projects at ht

Re: [CMake] Actual effect of set_source_files_properties with COMPILE_FLAGS - solved

Hello everybody, that's finally OK. Indeed; everything was OK. I did not pay attention that the flag was actually here. I was simply not looking in the right place. Perhaps new glasses or some rest should be my first resolution for 2012 !!! sorry for the inconvenience Eric pellegr

[CMake] Actual effect of set_source_files_properties with COMPILE_FLAGS

nes displayed are the one set in my set_compiler_flags macro. Is that just a bug on the display or is there something wrong with my settings ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France macro(set_compiler_flags) get

Re: [CMake] RC compiler on Linux - new problem

Fortran compiler identification is Intel -- Check for working Fortran compiler: /home/cs/pellegrini/bin/ifort -- Check for working Fortran compiler: /home/cs/pellegrini/bin/ifort -- works -- Detecting Fortran compiler ABI info -- Detecting Fortran compiler ABI info - done -- Checking whether /ho

[CMake] Determine 32 vs 64 bit cpu

() set(arch_64 FALSE) endif() thanks a lot and merry Christmas ! Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages

Re: [CMake] RC compiler on Linux - new problem

ied to use something like set_property(SOURCE myrcfile.rc PROPERTY RULE_LAUNCH_COMPILE ... in order to apply the patch only when a rc file is under process but unfortunately this property is not a valid source properties. Would you see any way to circumvent that problem ? thanks Eric pellegri

Re: [CMake] RC compiler on Linux - new problem - solved

thanks a lot Michael. Finally, this was not such a trivial problem but I should find my way with the examples you gave me. Eric Michael Hertling a écrit : On 10/21/2011 06:49 PM, pellegrini wrote: Hi all, after digging and googling some hours I did a first step in the right direction

Re: [CMake] RC compiler on Linux - new problem

.res but .o thanks for your help Eric pellegrini a écrit : Hi all, I use CMake 2.8.5 on Linux and Windows machine to build a Fortran project. On Windows, no problem, the build and the resulting GUI are OK. On Linux, the build seems to be OK but the resulting GUI gives an empty screen.

[CMake] RC compiler on Linux

specify to make cmake recognize and compile a rc file ? thanks Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep message

[CMake] Mixing static and dynamic library

get an error at link time (ld: cannot find -lXm). Would you have any idea of what is going wrong with my settings ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other Kitware open-source projects at ht

Re: [CMake] Linker flags not considered - solved

that's work ! Great ! Thanks a lot Rolf Rolf Eike Beer a écrit : On Mi., 12. Okt. 2011 17:05:52 CEST, pellegrini wrote: Hi all, I would like to build a project using intel fortran compiler. When building the project I would like to add/change two linker flags: - /

[CMake] Linker flags not considered

s also the /stack:12800 flag). I also try (by the way what is the difference ?): set(LINK_FLAGS "/stack:12800 /subsystem:windows") but it also produced the same unwanted effect. did I miss something somewhere ? thanks for your help Eric -- Eric Pellegrini Calcul Scient

Re: [CMake] CPACK_RESOURCE_FILE_WELCOME has no effect with NSIS - solved

This option is valid only for PackageMaker generator. I was not careful enough when looking at the doc :-[ sorry Eric pellegrini a écrit : Hi all, I would like to package my application using CPACK/NSIS generator. Using the following line: set(CPACK_RESOURCE_FILE_WELCOME

[CMake] CPACK_RESOURCE_FILE_WELCOME has no effect with NSIS

anks for your help Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- 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 CMake FAQ at:

Re: [CMake] modifying the PATH during NSIS intallation

forget my question. In the meantime, I solved my problem. For those interested, there is an option for this: CPACK_NSIS_MODIFY_PATH sorry Eric pellegrini a écrit : Hi all, I recently discovered the (very) useful CPack program from CMake. I would like to build an NSIS installer that, when

[CMake] modifying the PATH during NSIS intallation

) that fall in the scope of CPACK_INSTALL_COMMANDS ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages

Re: [CMake] Sharing objects between executables - solved

thanks for your help Alexander & Michael. Eric Michael Hertling a écrit : On 10/04/2011 10:42 AM, pellegrini wrote: Hi all, I would need your advise about the strategy to adopt when two executables share common object files. Sharing object files among different targets m

[CMake] Sharing objects between executables

best to my purpose ? If this is the second one: is there an easy way to get/specify the list of the object files generated during the console_prog build ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other

[CMake] Sharing objects between executables

to my purpose ? If this is the second one: is there an easy way to get/specify the list of the object files generated during the pfind build ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France -- Powered by www.kitware.com Visit other Kitware

Re: [CMake] multiple source directories - solved

thanks for the hints and your help, guys. Indeed, There was one '..\' too much in my source files path. Eric Andreas Pakulat a écrit : On 28.09.11 12:51:53, pellegrini wrote: Hi all, I have a project with the following structure: root/ CMakeLists.txt prog1/ CMak

[CMake] multiple source directories

with relative path when declaring the sources for a project. I tried using the option CMAKE_USE_RELATIVE_PATHS but it might not be defined for that purpose as it did not solve the problem. Would you have any idea how to solve that problem ? thanks a lot Eric -- Eric Pellegrini Calcul

Re: [CMake] The output of cpack is an empty file - solved

Eric Noulard a écrit : 2011/9/27 pellegrini : Hi Eric, thanks for your quick answer. No, my subprojects do not contains any CPack directives neither include cpack. Should they ? Sorry my fingers slipped. Another message is coming to the list. You need an INSTALL rule for each patr

[CMake] The output of cpack is an empty file

cmake and then nmake package, the built is done, cpack is launched but the resulting archive is empty. No README inside and more disturbing no prog1, prog2, prog3 executables. I may have miss something when reading the examples but I still have not found what. Would you have any idea ? t

Re: [CMake] LINKER FLAGS

thanks for the hint Eric & Michael Eric Michael Wild a écrit : On 09/13/2011 10:35 AM, pellegrini wrote: Hi all, I would like to build a Fortran90 project using Fortran intel compiler. I would like to increase the stack by adding the "/stack" flag to the linker.

[CMake] LINKER FLAGS

s wondering if using this command will remove the list of flags that may be set by cmake (behaviour that I would like to avoid) or just append it to this list ? thanks Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France __

Re: [CMake] Fwd: 64 bit flags

Thanks a lot Eric for the clear explanation. Eric Eric Noulard a écrit : I did forget the ML. -- Forwarded message -- From: Eric Noulard Date: 2011/9/9 Subject: Re: [CMake] 64 bit flags To: pellegrini 2011/9/9 pellegrini : Hello everybody, I have a Fortran project

[CMake] 64 bit flags

time or do I have to declare those flags through, for example, a '-D option ? thanks Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] EXECUTABLE_OUTPUT_PATH vs RUNTIME_OUTPUT_DIRECTORY

Michael Wild a écrit : On 07/22/2011 03:46 PM, pellegrini wrote: Hello everybody, I use CMake 2.8.4, Fortran 90 and Intel compiler to build an executable. I read in the documentation that RUNTIME_OUTPUT_DIRECTORY supercedes the old EXECUTABLE_OUTPUT_PATH command. When using

[CMake] EXECUTABLE_OUTPUT_PATH vs RUNTIME_OUTPUT_DIRECTORY

following files are created alongside my executable: - myexec.exe.embed.manifest - myexec.exe.embed.manifest.res - myexec.exe.intermediate.manifest - myexec.exe.resource.txt - myexec.ilk is there a way to get rid of these files ? thanks a lot Eric -- Eric Pellegrini Calcul

Re: [CMake] Problem running cmake 2.8.4 on Ubuntu 10.04

that cmake 2.8.0, 2.8.1, 2.82 works and starting from 2.8.3 the ABI steps fails. I may be wrong but it seems to be related to some "addings" in the version 2.8.3 and 2.8.4. Eric Alan W. Irwin a écrit : On 2011-07-06 11:36+0200 pellegrini wrote: Hello everybody, I have troubles runni

[CMake] Problem running cmake 2.8.4 on Ubuntu 10.04

identification is Intel -- Check for working Fortran compiler: /home/pellegrini/bin/ifort -- Check for working Fortran compiler: /home/pellegrini/bin/ifort -- works -- Detecting Fortran compiler ABI info CMake Error at /home/pellegrini/Downloads/cmake-2.8.4-Linux-i386/share/cmake-2.8/Modules

[CMake] Strange behaviour with -D option

command should have the last word. There should be something I completely missed. thanks a lot see you Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware ope

Re: [CMake] Post-build copy

Forget my question. I placed my add_custom_command at th wrong place ... sorry Eric pellegrini a écrit : Hello everybody, I build a static fortran library using CMake 2.8.0. Once the built is done I would like to copy the library archive and its related Fortran mod files stored in say

[CMake] Post-build copy

but nothing happens: ADD_CUSTOM_COMMAND( TARGET crysfml POST_BUILD COMMAND ${CMAKE_COMMAND} -E make_directory my_dir2 COMMAND ${CMAKE_COMMAND} -E copy_directory my_dir1 my_dir2) Am I doing something wrong ? Any idea ? thanks a lot See you Eric -- Eric Pellegrini Calcul

[CMake] Multiple output directories

. Any idea ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep

[CMake] Resource file skipped without warning

) ### I also read that there was a bug (http://www.cmake.org/Bug/view.php?id=4068) with CMake concerning ignored rc files without warning. Does my case fall in that category ? Would you have any hint to circumvent that problem ? thanks a lot Eric -- Eric Pellegrini Calcul

Re: [CMake] Add library at compiling time

Michael Wild a écrit : On 04/12/2011 04:52 PM, pellegrini wrote: Hello everybody, I am using CMake 2.8 on a Fortran 90 project using ifort compiler. I would like to specify the path for Winteracter graphical library not only when linking but also when compiling. By the way the library is

[CMake] Add library at compiling time

function but obviously as indicated by its name, it may do the job when linking but certainly not when compiling. Any idea ? thans in advance Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France ___ Powered by

[CMake] Problem using Lahey Fortran Compiler

e "hello world") the compilation works ? any idea thansks Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.

Re: [CMake] Merge two static libraries

window specific library? You could also use shared libraries (DLLs), but I guess that's out of the question for you, since you've been talking about static libraries only. Best regards, Marcel Loose. On Tue, 2010-10-05 at 10:45 +0200, pellegrini wrote: in fact the makefile we would l

Re: [CMake] Merge two static libraries

Loose a écrit : On 5-10-2010 at 10:10, in message <4caadd79.7000...@ill.fr>, pellegrini wrote: Hello everybody, I have a library that can be built for a use in different modes (console, window). It is made of two sets of files. The first one is common to the cons

[CMake] Merge two static libraries

thank you Eric -- Eric Pellegrini Calcul Scientifique Institut Laue-Langevin Grenoble, France ___ 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

Re: [CMake] Build several libraries with different compilation flags

r CMake to compile them again for my_lib2, because the object files are already up-to-date. I guess you'll have a better chance using target_properties, as Ryan suggested. HTH, Marcel Loose. On Fri, 2010-10-01 at 17:10 +0200, pellegrini wrote: Hi Ryan, Yes, that might be the solution

Re: [CMake] Build several libraries with different compilation flags

instead of the source file properties. Ryan On 10/01/2010 08:27 AM, pellegrini wrote: Hello everybody, I would like to build two libraries that contain the same files but with a slightly different set of compilation flags from one library to another. This within the same makefile. I was

[CMake] Build several libraries with different compilation flags

...) set_source_files_properties(file1, file2 ... PROPERTIES COMPILE_FLAGS ...) add_library(my_lib2, STATIC, src_files ...) set_source_files_properties(file1, file2 ... PROPERTIES COMPILE_FLAGS ...) does cmake sensitive to the order of these instruction ? thank you very much Eric -- Eric Pellegrini Calcul

[CMake] Overriding intel default compiler flags

g in that special case one of the cmake programming rules ? ! thanks for your help Eric -- Eric Pellegrini Calcul Scientifique Insitut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware open-source projects at http

[CMake] linker associated to ifort fortran compiler

txt file ? - as it actually uses 'lib', how cmake did find the appropriated linker ? thanks Eric -- Eric Pellegrini Calcul Scientifique Insitut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware open-so

Re: [CMake] cmake do not read my ifort compiler fllags - correct version

Marcel Loose a écrit : On Wed, 2010-09-29 at 12:06 +0200, pellegrini wrote: Hello everybody, I would like to set my own compiler flags to compile a library using intel fortran compiler. To do so, I created in my Src/ directory a "Compiler/Intel-Fortran.cmake" file that c

[CMake] cmake do not read my ifort compiler fllags - correct version

ile, it appears when building the cmake files. would you have any idea ? thanks Eric -- Eric Pellegrini Calcul Scientifique Insitut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitw

[CMake] cmake do not read my ifort compiler fllags

e I used to do the same with g95 and it worked perfectly. By the way, the flags used seem to be the ones set in the "Modules/Platform/Windows-ifort.cmake" cmake distribution, as if that file was parsed instead of mine ! would you have any idea ? than

Re: [CMake] Build library with specific compil flags for a few files

onvince my boss that using CMake is the right solution ... thanks again Eric > > On 28. Sep, 2010, at 16:08 , pellegrini wrote: > >> Hello everybody, >> >> I have a library for which almost all the files should be compiled (e.g. >> g95) with the same compilation f

[CMake] Build library with specific compil flags for a few files

dif() would you have any idea about how to esacpe from this kind of implementation ? is that so ugly ? thanks Eric -- Eric Pellegrini Calcul Scientifique Insitut Laue-Langevin Grenoble, France ___ Powered by www.kitware.com Visit other Kitware

[CMake] set_target_properties versus set_source_files_properties

it (so in that case "-O3" + "-O3 -std=f2003 -funroll-loops -msse2" giving "-O3 -O3 -std=f2003 -funroll-loops -msse2"). Am I right ? thanks a lot Eric -- Eric Pellegrini Calcul Scientifique Insitut Laue-Langevin Grenoble, France ___