<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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 Brad, Alan,<o:p></o:p></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">See below.<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: Tuesday, February 13, 2018 11:55 PM<br>
><br>
> In general, you get native packages from the mingw64 repository and POSIX-aware<br>
> packages from the msys2 repository for this dual-natured platform, and cmake is<br>
> one of those rare beasts that has a package in each repo.<br>
><br>
Yes, I have both – one in $PREFIX/mingw64/bin and one in $PREFIX/usr/bin. The latter is the MSYS2 version.<o:p></o:p></span></p>
<p><span style="font-size:10.0pt">> @Arjen: to answer Brad's questions you should modify our top-level CMakeLists.txt<br>
> to also report CMAKE_HOST_SYSTEM_NAME (just in case that is not the same<br>
> as CMAKE_SYSTEM_NAME which we already report there). ><br>
<br>
</span><o:p></o:p></p>
<p>The MinGW version of Cmake reports Windows for both variables and the MSYS2 version reports MSYS.<o:p></o:p></p>
<p>I set CC and FC to x64cc and nagfor respectively before invoking CMake (either version), so that the proper tools are used. However, the problem is that sometimes the configuration fails, sometimes the build fails. There is very little information about
what is going wrong. Or there is a lot I simply fail to find the wanted needle in that haystack.<o:p></o:p></p>
<p>I have also had a situation where the Freetype library was recognised but the build failed on a bunch of unresolved externals.<o:p></o:p></p>
<p>Further complication: my trial licence for NAG Fortran ends today <span style="font-family:Wingdings">
L</span>.<o:p></o:p></p>
<p>So, the exercise up to now has brought us a nice way to use NAG Fortran in its native environment, but without the benefit of installed packages under MinGW-w64/MSYS2.
<o:p></o:p></p>
<p>The number of combinations to try is also rather big, I am afraid. That would require a lot more trial and error, if no pruning is possible.<o:p></o:p></p>
<p>Regards,<o:p></o:p></p>
<p>Arjen<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>