[Cmake-commits] CMake branch, master, updated. v3.7.0-570-g706d05e

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20161117) +set(CMake_VERSION_PATCH 20161118) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] cm(Generator)Target::IsFrameworkOnApple

Gregor Jasny via cmake-developers wrote: > Hello, > > it looks like that during Generator Target refactoring the > cm(Generator)Target::IsFrameworkOnApple and similar got duplicated. Is > there a reason for this or could the GeneratorTarget simply query the > Target? Hi Gregor, The intention

[cmake-developers] cm(Generator)Target::IsFrameworkOnApple

Hello, it looks like that during Generator Target refactoring the cm(Generator)Target::IsFrameworkOnApple and similar got duplicated. Is there a reason for this or could the GeneratorTarget simply query the Target? Do you have by any chance some high level design documentation about the most

[Cmake-commits] CMake branch, next, updated. v3.7.0-1247-ga3fb155

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via a3fb155f636bbe567353b34b62c766ee19c43dae (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-1245-g077c70d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 077c70d310c18d7f93ca926e166316d645d30e7e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-1243-gf31f229

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via f31f22974fb00b2a63998947117ce7170afebbd6 (commit) via

Re: [CMake] Issue with Fortran/C binding with Intel compilers

Just to add my 2 cents to this. This past year a collaborator of mine updated his F95 code to F2003 and the ISO_C_BINDING syntax and this made the interaction between our C/C++ codes and their Fortran codes extremely easy. No more macros to try to figure out. It oddly, just seems to work. Well

Re: [CMake] Issue with Fortran/C binding with Intel compilers

Alan, Thanks for the advice, I think you are absolutely right, we should update to Fortran2003 to allow use of iso_c_binding module. Anyway I have actually been able to make CMake FortranCInterface work using a more recent version of CMake. Best, Joachim *Joachim Pouderoux*, PhD *Technical

Re: [CMake] Issue with Fortran/C binding with Intel compilers

On 2016-11-17 11:12-0400 Joachim Pouderoux wrote: Unfortunately I can't (Fortran95 only), that's why CMake feature is important. Hi Joachim: I have helped convert two projects (PLplot and the ephcom subproject of timeephem) recently to use the iso_c_binding module provided by Fortran 2003,

[Cmake-commits] CMake branch, next, updated. v3.7.0-1241-g073b3ae

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 073b3aef7631cff92db311c7df53dbf69b7d2100 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-1239-gaf3ae22

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via af3ae22aaa5397fe0b904b7de138740da402ad9e (commit) via

[CMake] CMake Project Generation Speedup

Hi all, We are still in the process of switching our large Make-based build to CMake. One of the issues we're running into is the time it takes to reparse and regenerate the CMake project (whether ninja, VS, or make) after touching any CMake file. To give you an idea, we have about 1000 targets

[Cmake-commits] CMake branch, next, updated. v3.7.0-1235-gdb1ee8a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via db1ee8ada8a5c3e4dc286772663b2b6d2da190b1 (commit) via

Re: [CMake] Issue with Fortran/C binding with Intel compilers

Unfortunately I can't (Fortran95 only), that's why CMake feature is important. Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2016-11-17 10:48 GMT-04:00 Elizabeth A. Fischer < elizabeth.fisc...@columbia.edu>: > Can you

Re: [CMake] Issue with Fortran/C binding with Intel compilers

Can you use the Fortran/C interop that is now an ISO standard for Fortran 2003 and beyond? That should eliminate the issues you're facing here. https://gcc.gnu.org/onlinedocs/gfortran/Interoperability-with-C.html On Thu, Nov 17, 2016 at 8:50 AM, Joachim Pouderoux <

[Cmake-commits] CMake branch, next, updated. v3.7.0-1233-gaa64072

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via aa6407263676127da94b4f5517410709fb47a2cc (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-565-ge67a59b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e67a59b00d08b426272c86771690782e5cc7f97f (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-569-g0e9634d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 0e9634d2c90fd748774f9238219cb1661550f233 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-561-g837d135

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 837d1359ee4d227476154d81de41f4af5ecf2c7c (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-563-g8dd3c31

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 8dd3c319c9baa60459df6b368440d8a7f0857580 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-1227-gdb48adf

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via db48adff5a6075554e2cd681bb0d4a5414af6e38 (commit) via

[CMake] Issue with Fortran/C binding with Intel compilers

Hi, I am using something like this in my CMake script: enable_language(Fortran) include(FortranCInterface) FortranCInterface_VERIFY() FortranCInterface_HEADER(${CMAKE_CURRENT_BINARY_DIR}/FortranBinding.h MACRO_NAMESPACE "FC_" SYMBOL_NAMESPACE "FC_") So far, with