[petsc-users] Compiling PETSc on Windows with Cygwin: errors with `win32fe cl`; okay to use `gcc`, `g++`, `gfortran` as compilers instead of `win32cf cl`?

[Satish Balay]

On Sat, 21 Nov 2015, Brian Merchant wrote:

> > [however you can't build petsc with cygwin/gnu compilers - and then
> link in with an application using MS compilers]
> 
> Could you tell me a little more about what you mean here? (sorry, I am a
> newbie) Is it that if I make an application say in Visual Studio, and
> attempt to use that application to call PETSc functions compiled with
> Cygwin, then I will run into trouble?

yes. Visual Studio uses Microsoft compilers - and you can link in
libraries compiled with cygwin/gnu compilers.

> 
> I contacted this group: http://www2.msic.ch/Software
> and got the latest build from them that is supposed to work with Visual
> Studio; which addresses your MS compilers concern?

If you require to use PETSc from Visual studio - then this would be one option.
[however the website lists petsc-3.5 - not the latest pets-3.6]

> 
> However, I also want to use petsc4py Python bindings with PETSc, so I
> shouldn't be in trouble there if I use Cygwin, right?

Yes - petsc4py should work with cygwin/gnu compiler build of PETSc
[with cygwin python]

With cygwin - you can install liblapack-devel, libopenmpi-devel [with
cygwin setup.exe] and use them to build PETSc and petsc4py

Satish