Re: [CMake] .vfproj with cmake

lokmane.abbas-turki wrote: Hi, I have already sent this email but I still don't receive an answer. Could you please tell me what should I do to build a simple .vfproj with cmake without a version conflict. CMake does not support this version currently. To fix it temporarily you can ha

Re: [CMake] Fortan and C++

You are well informed. So this standard is implemented in icc/ifort 11.x but not (yet) GNU? This renders the FortranCInterface.cmake rather obsolete, does it not? Yes, it looks rather excessive, but at least clean. Thanks, Dominik Michael Wild wrote: On 22. Aug, 2009, at 15:29, Dominik Szcze

Re: [CMake] Fortan and C++

Of course, you are right - not about ifcore that is resolved by ldd, but about the multibyte magic. I applied your patch. Now I get: -- checking Fortran function linkage: sub_ -- found Fortran function linkage -- checking Fortran function with _ linkage: my_sub_ -- checking Fortran module linka

Re: [CMake] Fortan and C++

On 22. Aug, 2009, at 15:29, Dominik Szczerba wrote: [...] If you try to use FortranCInterface.cmake, be aware that it is quite buggy, as it doesn't pass the CMAKE_*_FLAGS to the try_compile calls. Further it doesn't ensure that the C language is enabled, altough it is calling try_compile

Re: [CMake] Fortan and C++

As I said, FortranCInterface.cmake is buggy as it doesn't pass the CMAKE_Fortran_FLAGS and CMAKE_EXE_LINKER_FLAGS variables to the TRY_COMPILE project. If you have to set these in order to compile/link a mixed-language program, it fails. Come to think of it, in your case the ifcore library

Re: [CMake] Fortan and C++

I naively tried: INCLUDE(FortranCInterface) CREATE_FORTRAN_C_INTERFACE(myf cross myfconfig.h) to get: -- checking Fortran function linkage: sub_ -- checking Fortran function linkage: _sub_ -- checking Fortran function linkage: __sub_ -- checking Fortran function linkage: SUB_ -- checking Fortra

Re: [CMake] Fortan and C++

Hi Michael, Michael Wild wrote: Hi Dominik Concerning the flags: you should add the -no-multibyte-chars to the CMAKE_CXX_FLAGS variable. This will get prepended to all CMAKE_CXX_FLAGS_{RELEASE,DEBUG,...} flags, since you don't want this flag to be used for the Release configuration exclus

Re: [CMake] Fortan and C++

Reported the issue with FortranCInterface.cmake here: http://www.vtk.org/Bug/view.php?id=9446 Michael On 22. Aug, 2009, at 14:03, Michael Wild wrote: Hi Dominik Concerning the flags: you should add the -no-multibyte-chars to the CMAKE_CXX_FLAGS variable. This will get prepended to all CM

Re: [CMake] Fortan and C++

Hi Dominik Concerning the flags: you should add the -no-multibyte-chars to the CMAKE_CXX_FLAGS variable. This will get prepended to all CMAKE_CXX_FLAGS_{RELEASE,DEBUG,...} flags, since you don't want this flag to be used for the Release configuration exclusively, but for all configuration

Re: [CMake] Fortan and C++

Here the report of my tests: Just ignorant approach (don't google): It works out of the box on linux with intel compilers 10.x. Just add Fortran to the languages in the project signature and add STUFF.F90 to the source files. You need to link to ifcore library though. It does not work out of

Re: [CMake] .vfproj with cmake

Hi, I have already sent this email but I still don't receive an answer. Could you please tell me what should I do to build a simple .vfproj with cmake without a version conflict.   Best regards. Lokman. > > OK, can you try this. > > > 1. Run cmake --debug-trycompile > > 2. Do not load the pro

Re: [CMake] Fortan and C++

Michael, Many thanks for the feedback. What I am doing with a GNU makefile so far is compile just one file with the fortran compiler use C++ linker to link all object files as usual. A comprehensive solution I would expect in cmake would be 1) nothing (.f90 file is understood) or something along