If someone sends me the instructions, I can create the pull request (my
experience with git is that each project has very particular requirements and
things go better if I follow each projects specific checklist).
Bill
William Gropp
Director and Chief Scientist, NCSA
Thomas M. Siebel Chair in
Bill,
The generic pull request instructions are at:
https://bitbucket.org/petsc/petsc/wiki/Home#markdown-header-contributing-to-petsc
https://bitbucket.org/petsc/petsc/wiki/pull-request-instructions-git
Some of the instructions are wrt a fork. With write access to the
petsc repo - you can
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
Ah, OK. I was originally just thinking that many people would be happy if they
can get PETSc to simply work with GCC or Clang that they get from the package
manager used in the WSL setup. I believe both the Microsoft and Intel compilers
are all available for free these days, so I'll install
This discussion comes up each time a user has issues with cygwin.
For any alternate system, we would have to redo win32fe functionality for that
system.
* Marshal gcc type compiler options to Cl
* Convert paths in some of these options from this system ( for ex cygwin
paths) to
Richard,
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).
Barry
> On Jul 1, 2019, at 3:59 PM, Mills, Richard Tran via
https://bitbucket.org/petsc/petsc/pull-requests/1836/installationhtml-edited-online-with/diff
I try to provide a better guild for Windows possibilities without windows
compilers. (Could probably do with some light editing). Maybe more options?
Satish,
At the bottom of the Windows
