Re: [CMake] Reason of Fortran include directories /config?
Thanks very much for the feedback. I will look into the module stuff, where the compiler puts it etc. Petr On Wed, May 16, 2012 at 10:24 PM, Brad King brad.k...@kitware.com wrote: On 05/10/2012 03:25 AM, Petr Kmoch wrote: we're using cmake to generate Intel Fortran .vfproj files and some of my developers were asking why include directories in the project always include X and X/config_name for every directory X specified via include_directories(). Looking at cmake source code, the lines responsible seem to be 829-837 of cmLocalVisualStudio7Generator.cxx The lines were added as part of the original Fortran support: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=10c91ded#patch6 I would be really interested in the reason for this behaviour. Could anyone shed some light onto this for me? As Michael pointed out this probably has to do with Fortran 90 .mod files. The Intel compiler loads them from the include files search path. Contents of .mod files may be configuration-specific so perhaps the compiler puts them in the per-config output directories. I was not personally involved in adding those particular lines though. -Brad -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Reason of Fortran include directories /config?
Anyone? Surely there must be a reason for adding those directories. Petr On Thu, May 10, 2012 at 9:25 AM, Petr Kmoch petr.km...@gmail.com wrote: Hi all, we're using cmake to generate Intel Fortran .vfproj files and some of my developers were asking why include directories in the project always include X and X/config_name for every directory X specified via include_directories(). Looking at cmake source code, the lines responsible seem to be 829-837 of cmLocalVisualStudio7Generator.cxx (in the 2.8.8 released archive): // if this is fortran then output the include with // a ConfigurationName on the end of it. if(this-FortranProject) { ipath = i-c_str(); ipath += /$(ConfigurationName); ipath = this-ConvertToXMLOutputPath(ipath.c_str()); fout ipath ;; } } I would be really interested in the reason for this behaviour. Could anyone shed some light onto this for me? Thanks in advance. Petr -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Reason of Fortran include directories /config?
My guess is that it has something to do with module files. Michael On 05/16/2012 08:31 AM, Petr Kmoch wrote: Anyone? Surely there must be a reason for adding those directories. Petr On Thu, May 10, 2012 at 9:25 AM, Petr Kmoch petr.km...@gmail.com wrote: Hi all, we're using cmake to generate Intel Fortran .vfproj files and some of my developers were asking why include directories in the project always include X and X/config_name for every directory X specified via include_directories(). Looking at cmake source code, the lines responsible seem to be 829-837 of cmLocalVisualStudio7Generator.cxx (in the 2.8.8 released archive): // if this is fortran then output the include with // a ConfigurationName on the end of it. if(this-FortranProject) { ipath = i-c_str(); ipath += /$(ConfigurationName); ipath = this-ConvertToXMLOutputPath(ipath.c_str()); fout ipath ;; } } I would be really interested in the reason for this behaviour. Could anyone shed some light onto this for me? Thanks in advance. Petr -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Reason of Fortran include directories /config?
On 05/10/2012 03:25 AM, Petr Kmoch wrote: we're using cmake to generate Intel Fortran .vfproj files and some of my developers were asking why include directories in the project always include X and X/config_name for every directory X specified via include_directories(). Looking at cmake source code, the lines responsible seem to be 829-837 of cmLocalVisualStudio7Generator.cxx The lines were added as part of the original Fortran support: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=10c91ded#patch6 I would be really interested in the reason for this behaviour. Could anyone shed some light onto this for me? As Michael pointed out this probably has to do with Fortran 90 .mod files. The Intel compiler loads them from the include files search path. Contents of .mod files may be configuration-specific so perhaps the compiler puts them in the per-config output directories. I was not personally involved in adding those particular lines though. -Brad -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Reason of Fortran include directories /config?
Hi all, we're using cmake to generate Intel Fortran .vfproj files and some of my developers were asking why include directories in the project always include X and X/config_name for every directory X specified via include_directories(). Looking at cmake source code, the lines responsible seem to be 829-837 of cmLocalVisualStudio7Generator.cxx (in the 2.8.8 released archive): // if this is fortran then output the include with // a ConfigurationName on the end of it. if(this-FortranProject) { ipath = i-c_str(); ipath += /$(ConfigurationName); ipath = this-ConvertToXMLOutputPath(ipath.c_str()); fout ipath ;; } } I would be really interested in the reason for this behaviour. Could anyone shed some light onto this for me? Thanks in advance. Petr -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake