<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<link rel="Stylesheet" type="text/css" media="all" href="mailoffice.css"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Arial","sans-serif";
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple" id="notables">
<div class="WordSection1">
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi Alan,<o:p></o:p></span></p>
<p><span style="font-size:10.0pt">> -----Original Message-----<br>
> From: Alan W. Irwin [<a href="mailto:irwin@beluga.phys.uvic.ca">mailto:irwin@beluga.phys.uvic.ca</a>]<br>
> Sent: Thursday, February 08, 2018 10:59 PM<br>
> To: Arjen Markus<br>
> Cc: cmake@cmake.org<br>
> Subject: Re: [CMake] MinGW-w64/MSYS2 (or Cygwin) and NAG Fortran - how to<br>
> combine?<br>
><br>
> On 2018-02-08 19:33-0000 Arjen Markus wrote:<br>
><br>
> > So: Is it possible to instruct CMake to use the NAG-Fortran specific<br>
> settings [for the Cygwin and MinGW-w64/MSYS2 platforms] and if so, how do I do<br>
> that?<br>
><br>
> Hi Arjen:<br>
><br>
> I think you should be guided by what goes on for gfortran. For that compiler, the<br>
> relevant Platform files are called CYGWIN-GNU-Fortran.cmake and Windows-<br>
> GNU-Fortran.cmake Platform files for the Cygwin, and MinGW-w64/MSYS2<br>
> platforms. Furthermore, in all the existing nagfor cases (Linux and Darwin), you<br>
> derive the nagfor-related name from the gfortran related name by replacing GNU-<br>
> Fortran by NAG-Fortran. Therefore, I suggest you try the names CYGWIN-NAG-<br>
> Fortran.cmake and Windows-NAG-Fortran.cmake for the two separate Platform<br>
> files you are trying to create for the Cygwin and<br>
> MinGW-w64/MSYS2 platforms.<br>
><br>
I have a Platform file “Windows-NAG-Fortran.cmake” and that is used correctly if I start the NAG Fortran environment (using the MinGW Makefiles generator), but if I try the same with MinGWw-w64/MSYS2, this file is clearly ignored – I see the compiler fail on
a typical GCC flag for creating shared libraries (the Platform file I added takes care of that in the NAG Fortran environment and therefore the build succeeds).<o:p></o:p></span></p>
<p><span style="font-size:10.0pt">My guess is that the environment is determined in an early stage and then GNU/GCC has already been selected. But not all is lost – I realised that I may be able to get around this by expanding the PATH with the MinGW-w64/MSYS2
specific directories. I have not tried that yet.<o:p></o:p></span></p>
<p><span style="font-size:10.0pt">Though I am still interested in other solutions ;).<o:p></o:p></span></p>
<p><span style="font-size:10.0pt">Regards,<o:p></o:p></span></p>
<p><span style="font-size:10.0pt">Arjen<o:p></o:p></span></p>
<p><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p><o:p> </o:p></p>
</div>
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure
or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from
the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
</body>
</html>