<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi John,</p>
<p>A few comments:<br>
</p>
<ul>
<li>The existing PR's have languished for some time because most of us with MOAB expertise have very little Windows experience. I'm not sure it's worth waiting for them to be merged first if you already have a Windows port working.</li><li>One of the goals of PR405 was to minimize dependencies for a minimally acceptable build. To that end, it avoids relying on LAPACK/BLAS because that comes with FORTRAN expectations, which comes with FORTRAN compiler needs, all of which explode the dependencies.
We also wanted to minimize how intrusive we were. We were able to build it with only:</li><ul>
<li>VisualStudio C++</li><li>CMake</li><li>HDF5</li><li>Eigen3<br>
</li></ul>
<li>Does your port presume that Bilder is being used?</li></ul>
<p>Thanks,</p>
<p>Paul<br>
</p>
<div class="moz-cite-prefix">On 10/22/19 10:55, John R Cary via moab-dev wrote:<br>
</div>
<blockquote type="cite" cite="mid:03ba5725-b7be-cb3d-4c9e-683d153f888e@txcorp.com">
<tt>Thanks, Paul. We do have Moab ported to Windows and working, so we could<br>
set a PR, but first we have to sync-up, and there are lots of conflicts.<br>
<br>
So before we start on this, we would prefer that all other work on Windows<br>
ports be in so that we do not duplicate effort. Would this be possible<br>
in a modest amount of time?<br>
<br>
In response to Vijay -- we build our toolchain on multiple platforms<br>
(Windows VS, Windows LLVM, macOS same, Linux various compilers) using<br>
Jenkins as the driver and our own Bilder as a package manager for building<br>
and running tests.<br>
<br>
To make sure I understand, we should branch off master -- after you get<br>
current PRs in. Then add our code. Then submit a pull request to your<br>
develop. Is this right?<br>
<br>
Thx.....John<br>
</tt><br>
<div class="moz-cite-prefix">On 10/22/19 11:27 AM, Paul Wilson wrote:<br>
</div>
<blockquote type="cite" cite="mid:73f6a014-f708-e251-3af7-cb304da62484@wisc.edu">
<p>Hi John,</p>
<p>There have been a few attempts at a Windows port - or partial windows ports - that live in branches and/or PRs. I'm most familiar with this one:
<a href="https://bitbucket.org/fathomteam/moab/pull-requests/405" moz-do-not-send="true">
https://bitbucket.org/fathomteam/moab/pull-requests/405</a> that Baptiste worked on.</p>
<p>Paul<br>
</p>
<div class="moz-cite-prefix">On 10/22/19 10:11, John R Cary via moab-dev wrote:<br>
</div>
<blockquote type="cite" cite="mid:2f605eb3-7de7-d3ec-ea87-8ddda9ddaf2c@txcorp.com">
<tt>Thanks, Vijay. <br>
<br>
On a related note, we had started porting Moab to Windows. When merging<br>
our changes to your develop branch, we found a number of conflicts.<br>
<br>
Did you port Moab to Windows?<br>
<br>
And you still want pull requests to your develop branch?<br>
<br>
Thx.....John<br>
</tt><br>
<div class="moz-cite-prefix">On 10/22/19 10:24 AM, Vijay S. Mahadevan wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAOcbyd0e4WvWp6kvVGtcrfFyXUAsvWoebF9pMBWUm+O_mFJQRQ@mail.gmail.com">
<div dir="auto">John,
<div dir="auto"><br>
</div>
<div dir="auto">AFAIK, no one has verified this. If you already have some checks, please let us know and we will try to fix incompatibility. Or if you can submit changes as PRs, thst would be much appreciated. </div>
<div dir="auto"><br>
</div>
<div dir="auto">I do want to note that MOAB is C++03 compliant still and we only recently started adding new dependencies that have C++11 requirements. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks, </div>
<div dir="auto">Vijay </div>
<br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">On Tue., Oct. 22, 2019, 8:58 a.m. John R Cary via moab-dev, <<a href="mailto:moab-dev@mcs.anl.gov" moz-do-not-send="true">moab-dev@mcs.anl.gov</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
We have recently ported most of our build chain to c++17.<br>
However, our fork of moab is not c++-17 compliant. Is the<br>
main repo c++17 compliant?<br>
<br>
Thx....John Cary<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</blockquote>
<div class="moz-signature">-- <br>
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --<br>
Paul P.H. Wilson (he/him/his)<br>
Grainger Professor of Nuclear Engineering<br>
Chair, <a href="http://engr.wisc.edu/ep" moz-do-not-send="true">Department of Engineering Physics</a><br>
Chair, <a href="http://eap.wisc.edu" moz-do-not-send="true">Energy Analysis and Policy Certificate</a><br>
608-263-0807<br>
<a class="moz-txt-link-abbreviated" href="mailto:paul.wilson@wisc.edu" moz-do-not-send="true">paul.wilson@wisc.edu</a><br>
153 Engineering Research Bldg<br>
1500 Engineering Dr, Madison, WI 53706
<p><a href="http://cnerg.engr.wisc.edu" moz-do-not-send="true">Computational Nuclear Engineering Research Group</a><br>
</p>
</div>
</blockquote>
<br>
</blockquote>
<div class="moz-signature">-- <br>
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --<br>
Paul P.H. Wilson (he/him/his)<br>
Grainger Professor of Nuclear Engineering<br>
Chair, <a href="http://engr.wisc.edu/ep">Department of Engineering Physics</a><br>
Chair, <a href="http://eap.wisc.edu">Energy Analysis and Policy Certificate</a><br>
608-263-0807<br>
<a class="moz-txt-link-abbreviated" href="mailto:paul.wilson@wisc.edu">paul.wilson@wisc.edu</a><br>
153 Engineering Research Bldg<br>
1500 Engineering Dr, Madison, WI 53706
<p><a href="http://cnerg.engr.wisc.edu">Computational Nuclear Engineering Research Group</a><br>
</p>
</div>
</body>
</html>