<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
.x_MsoChpDefault
{}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div lang="EN-US" link="blue" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">This discussion comes up each time a user has issues with cygwin.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">For any alternate system, we would have to redo win32fe functionality for that system.</p>
<p class="x_MsoNormal"> </p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">Marshal gcc type compiler options to Cl</li><li class="x_MsoListParagraph" style="margin-left:0in">Convert paths in some of these options from this system ( for ex cygwin paths) to Windows paths.</li><li class="x_MsoListParagraph" style="margin-left:0in">Have python that works with system path notation.</li><li class="x_MsoListParagraph" style="margin-left:0in">Have the ability equivalent to Windows process spawning cygwin process spawning Windows process. Wsl1 lacked this. Don't know about wsl2..
</li></ul>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Current issue with cygwin was some bash config issue. Even if we manage to port build tools to wsl2 or alternative system, such sub-tool issues can still come up in the new system.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Satish</p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="border:none; padding:0in"><b>From: </b><a href="mailto:petsc-dev@mcs.anl.gov">Smith, Barry F. via petsc-dev</a><br>
<b>Sent: </b>Monday, July 1, 2019 2:17 PM<br>
<b>To: </b><a href="mailto:rtmills@anl.gov">Mills, Richard Tran</a><br>
<b>Cc: </b><a href="mailto:petsc-dev@mcs.anl.gov">petsc-dev@mcs.anl.gov</a><br>
<b>Subject: </b>Re: [petsc-dev] alternatives to cygwin on Windows with PETSc</p>
</div>
<p class="x_MsoNormal"> </p>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText"><br>
Richard,<br>
<br>
Thanks. The important thing is to be able to build PETSc for Microsoft and Intel Windows compilers (so that users can use the libraries from the Microsoft development system as a "regular" Windows users).<br>
<br>
Barry<br>
<br>
<br>
> On Jul 1, 2019, at 3:59 PM, Mills, Richard Tran via petsc-dev <petsc-dev@mcs.anl.gov> wrote:<br>
> <br>
> I played around with WSL1 quite some time ago and it seemed pretty promising. I have not tried WSL2, but I'm guessing that it may be the best option for building PETSc on a Windows 10 machine. I've got a Windows 10 machine (it basically just runs my television/media
center) and I'll give it a try on there.<br>
> <br>
> --Richard<br>
> <br>
> On 6/29/19 8:11 PM, Jed Brown via petsc-dev wrote:<br>
>> "Smith, Barry F. via petsc-dev" <petsc-dev@mcs.anl.gov><br>
>> writes:<br>
>> <br>
>> <br>
>>> Does it make sense to recommend/suggest git bash for Windows as an alternative/in addition to Cygwin?<br>
>>> <br>
>> I would love to be able to recommend git-bash and/or WSL2 (which now<br>
>> includes a full Linux kernel). I don't have a system on which to test,<br>
>> but it should be possible to make it work (if it doesn't already).<br>
>> <br>
> <br>
<br>
</div>
</span></font>
</body>
</html>