<div dir="ltr"><div>Hi,<br></div>It seems that try run does not support Fortran. Is this indeed the case?<br><div><div><div class="gmail_extra"><br></div><div class="gmail_extra">When I use try_run() in my CMakeLists.txt I get the following error:<br>
<br>
<style type="text/css">
p, li { white-space: pre-wrap; }
</style>
<p style="margin:0px;text-indent:0px"><span style="color:rgb(255,0,0)">CMake Error at CMakeLists.txt:9 (ADD_EXECUTABLE):</span></p>
<p style="margin:0px;text-indent:0px;color:rgb(255,0,0)"> Cannot find source file:</p>
<p style="margin:0px;text-indent:0px;color:rgb(255,0,0)"> getbigint.f90</p>
<p style="margin:0px;text-indent:0px;color:rgb(255,0,0)"> Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp</p>
<p style="margin:0px;text-indent:0px;color:rgb(255,0,0)"> .hxx .in .txx</p>
<p style="margin:0px;text-indent:0px;color:rgb(255,0,0)">CMake Error: Internal CMake error, TryCompile generation of cmake failed</p><br></div><div class="gmail_extra">It seems that C and C++ are supported, but not Fortran. Is this correct? Should I file a bug report/feature request?<br>
<br></div><div class="gmail_extra"><div>Izaak Beekman<br>===================================<br>(301)244-9367<br>UMD-CP Visiting Graduate Student<br>Aerospace Engineering<br><a href="mailto:ibeekman@umiacs.umd.edu" target="_blank">ibeekman@umiacs.umd.edu</a><br>
<a href="mailto:ibeekman@umd.edu" target="_blank">ibeekman@umd.edu</a></div>
<br><br><div class="gmail_quote">On Wed, Oct 2, 2013 at 12:00 PM, <span dir="ltr"><<a href="mailto:cmake-request@cmake.org" target="_blank">cmake-request@cmake.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Send CMake mailing list submissions to<br>
<a href="mailto:cmake@cmake.org">cmake@cmake.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cmake-request@cmake.org">cmake-request@cmake.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cmake-owner@cmake.org">cmake-owner@cmake.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of CMake digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [cmake-developers] CMake 2.8.12-rc4 ready for testing!<br>
(Nicolas Despr?s)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 2 Oct 2013 15:31:49 +0200<br>
From: Nicolas Despr?s <<a href="mailto:nicolas.despres@gmail.com">nicolas.despres@gmail.com</a>><br>
Subject: Re: [CMake] [cmake-developers] CMake 2.8.12-rc4 ready for<br>
testing!<br>
To: Robert Maynard <<a href="mailto:robert.maynard@kitware.com">robert.maynard@kitware.com</a>><br>
Cc: CMake Developers <<a href="mailto:cmake-developers@cmake.org">cmake-developers@cmake.org</a>>, <a href="mailto:kde-devel@kde.org">kde-devel@kde.org</a>,<br>
CMake MailingList <<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAPqtr1%2BD3ifsCtWoqU7z2shJ7JjS6QtcoGhShaDqAwqyBTMhSQ@mail.gmail.com">CAPqtr1+D3ifsCtWoqU7z2shJ7JjS6QtcoGhShaDqAwqyBTMhSQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi,<br>
<br>
I have just download, compile and run the test suite on my Linux machine<br>
and I have two failing tests:<br>
<br>
The following tests FAILED:<br>
25 - FindPackageTest (Failed)<br>
291 - CTestTestMemcheckDummyValgrindInvalidSupFile (Failed)<br>
<br>
This is probably due to my setup. I have attached the log to this post.<br>
<br>
Cheers,<br>
-Nico<br>
<br>
<br>
<br>
<br>
<br>
On Tue, Oct 1, 2013 at 10:49 PM, Robert Maynard<br>
<<a href="mailto:robert.maynard@kitware.com">robert.maynard@kitware.com</a>>wrote:<br>
<br>
> The CMake 2.8.12 release candidate stream continues!<br>
> Thanks to numerous CMake users we uncovered a couple of critical<br>
> regressions<br>
> in RC3. We expect that RC4 will be the final RC unless a new critical,<br>
> regression is discovered. You can find the source and binaries here:<br>
> <a href="http://www.cmake.org/files/v2.8/?C=M;O=D" target="_blank">http://www.cmake.org/files/v2.8/?C=M;O=D</a><br>
><br>
> Some of the notable changes in this release are:<br>
><br>
> - Introduced target_compile_options command<br>
> - Specify compile options to use when compiling a given target. Supports<br>
> PUBLIC, PRIVATE, and INTERFACE options. PRIVATE and PUBLIC items will<br>
> populate the COMPILE_OPTIONS property of the target. PUBLIC and<br>
> INTERFACE items will populate the INTERFACE_COMPILE_OPTIONS property<br>
> of the target. Supports generator expressions.<br>
> - Introduced add_compile_options command<br>
> - Adds options to the compiler command line for sources in the<br>
> current directory and below. Supports generator expressions.<br>
> - Introduced CMake Policy CMP0021:<br>
> - It is now an error to add relative paths to the INCLUDE_DIRECTORIES<br>
> target property.<br>
> - Introduced CMake Policy CMP0022:<br>
> - Target properties matching<br>
> (IMPORTED_)LINK_INTERFACE_LIBRARIES(_<CONFIG>)<br>
> are ignored, and will no longer be populated by the<br>
> target_link_libraries<br>
> command. It is now an error to populate the properties directly in user<br>
> code. Instead use the INTERFACE keyword with target_link_libraries, or<br>
> the target property INTERFACE_LINK_LIBRARIES.<br>
> - Introduced CMake Policy CMP0023:<br>
> - Plain and keyword target_link_libraries signatures cannot be mixed for<br>
> a<br>
> given target when this policy is enabled. Once PUBLIC,PRIVATE, or<br>
> INTERFACE keywords are used, all subsequent target_link_libraries calls<br>
> to the target must use one of these keywords.<br>
> - Introduced: Support for RPATH under OSX<br>
> - Please see the blog post by Clinton Stimpson about using RPATH on OSX<br>
> (<a href="http://www.kitware.com/blog/home/post/510" target="_blank">http://www.kitware.com/blog/home/post/510</a>)<br>
><br>
> - CMake: New PUBLIC PRIVATE and INTERFACE options for target_link_libraries<br>
> - CMake: New ALIAS targets feature<br>
> - CMake: Automatically process Headers directory of Apple Frameworks as<br>
> a usage requirement<br>
> - CMake: File command now supports the GENERATE command to produce files at<br>
> generate time<br>
> - CMake: target_include_directories now supports the SYSTEM parameter<br>
> - CMake: Add support for Java in cross compilation toolchains<br>
> - CMake: Improved support for the IAR toolchain<br>
> - CMake: Improved support for the ARM toolchain under Visual Studio<br>
> - CMake: Improvements to the Visual Studio Generators Including<br>
> - Separate compiler and linker PDB files<br>
> - Support for subdirectory MSBuild projects<br>
> - Support for assembly code to VS10<br>
> - Support for Windows CE to VS11<br>
> - CMake: Added COMPILE_OPTIONS target property.<br>
> - CMake: Added INTERFACE_LINK_LIBRARIES added as a property to targets<br>
> - CMake: Now supports .zip files with the tar command<br>
> - CMake: try_compile now supports multiple source files<br>
> - CMake: Optimized custom command dependency lookup<br>
> - CMake: Removal of configured files will retrigger CMake when issuing a<br>
> build command<br>
> - CMake: Ninja now tracks custom command generated files that aren't listed<br>
> as output<br>
> - CMake: Added generator expression support for compiler versions<br>
> - CMake-Gui: Add search functions for Output window<br>
> - CTest: Improved memory checker support<br>
> - FindGTK2: General Improvements<br>
> - FindCUDA: Multiple improvements to the custom commands<br>
><br>
><br>
> The bug tracker change log page for this version is at:<br>
> <a href="http://public.kitware.com/Bug/changelog_page.php?version_id=112" target="_blank">http://public.kitware.com/Bug/changelog_page.php?version_id=112</a><br>
><br>
> The complete list of changes in RC4 since RC3 can be found at:<br>
> <a href="http://www.cmake.org/Wiki/CMake/ChangeLog" target="_blank">http://www.cmake.org/Wiki/CMake/ChangeLog</a><br>
><br>
> As this is expected to be the last RC release please test it and report any<br>
> regressions to the list or the bug tracker.<br>
><br>
> Thanks<br>
> --<br>
><br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the CMake FAQ at:<br>
> <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers</a><br>
><br>
<br>
<br>
<br>
--<br>
Nicolas Despr?s<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.cmake.org/pipermail/cmake/attachments/20131002/4f235e80/attachment-0001.htm" target="_blank">http://www.cmake.org/pipermail/cmake/attachments/20131002/4f235e80/attachment-0001.htm</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: test.log<br>
Type: application/octet-stream<br>
Size: 4705 bytes<br>
Desc: not available<br>
URL: <<a href="http://www.cmake.org/pipermail/cmake/attachments/20131002/4f235e80/attachment-0001.obj" target="_blank">http://www.cmake.org/pipermail/cmake/attachments/20131002/4f235e80/attachment-0001.obj</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
<br>
End of CMake Digest, Vol 114, Issue 4<br>
*************************************<br>
</blockquote></div><br></div></div></div></div>