On Wed, Nov 30, 2016 at 6:03 AM, Boris Kaus wrote:
>
> > This is probably a better choice than Cygwin going forward.
> >
> > https://msdn.microsoft.com/en-us/commandline/wsl/about
> >
> > I don't know to what extent PETSc users have experimented with this
> > feature, but it should make it easier
Hi Elaine,
The PETSc configured/built in Cygwin can be normally used outside of it.
It can either be statically linked with your software, or linked as a .DLL
and deployed normally :).
On Mon, Nov 28, 2016 at 1:49 PM, Elaine Tang wrote:
> Hi,
>
> I am developing some software on windows that
> This is probably a better choice than Cygwin going forward.
>
> https://msdn.microsoft.com/en-us/commandline/wsl/about
>
> I don't know to what extent PETSc users have experimented with this
> feature, but it should make it easier to build and distribute PETSc.
We have tried this in Mainz, and
May I propose docker as an alternative approach? https://www.docker.com
There are already petsc images and creating your own environment is not
that hard. As a bonus you get a cross platform solution ... unless your
application is windows specific in which case docker might not be the best
way to
Elaine Tang writes:
> I am developing some software on windows that would like to utilize petsc
> library. Currently I have petsc library configured on cygwin on my windows
> machine.
This is probably a better choice than Cygwin going forward.
https://msdn.microsoft.com/en-us/commandline/wsl/ab
