[Bf-committers] MinGW support

[Yousef Harfoush]

> supporting a proper development environment requires installing visual
> studio/Windows SDK anyway, so it sort of defeats the purpose of having an
> "independent" compiler.
ms is released a c++ environment without the VS IDE, it is not that big requirement.

> Only positive thing from MinGW side as far as I know is faster cycles, but
> it's been a while since I tested this. It may be better now with 2013
> compiler?

but is it not worth 40% render time reduction to support mingw, i mean that's is like 2 years of optimizing cycles, isn't it, i think it's better to drop vc12 in favor of mingw.




Regards
Yousef Harfoush
bat3a at msn.com



> Date: Sat, 26 Dec 2015 21:30:18 +0100
> From: kalast at gmail.com
> To: bf-committers at blender.org
> Subject: Re: [Bf-committers] MinGW support
> 
> Hi,
> 
> Status with openmp as far as I know is fine. The problem with MinGW is that
> supporting a proper development environment requires installing visual
> studio/Windows SDK anyway, so it sort of defeats the purpose of having an
> "independent" compiler.
> 
> * MSVC is needed to compile CUDA binaries
> * MSVC is needed to run a debug build, since python is lined against the
> debug libraries of microsoft, not MinGW.
> * Debugging threads is not so well/natively supported (since pthread
> library of MinGW is built on top of win32 library)
> 
> Only positive thing from MinGW side as far as I know is faster cycles, but
> it's been a while since I tested this. It may be better now with 2013
> compiler?
> I wouldn't want to spend any more time maintaining this, so if anyone wants
> to take over (supposing we decide it is even worth it) be my guest.
> 
> On 26 December 2015 at 19:47, Sergey Sharybin <sergey.vfx at gmail.com> wrote:
> 
> > We can not advertise some sort of franken-compiler as an officially
> > supported. Either the issues are solved in upstream or we don't consider
> > compiler officially supported.
> >
> > On Sat, Dec 26, 2015 at 11:44 PM, Yousef Harfoush <bat3a at msn.com> wrote:
> >
> > > > Date: Sat, 26 Dec 2015 23:08:42 +0500
> > > > From: sergey.vfx at gmail.com
> > > > To: bf-committers at blender.org
> > > > Subject: Re: [Bf-committers] MinGW support
> > > >
> > > > If we're going to keep supporting MinGW it should be latest official
> > > > version. I remember we were having major issues with some system
> > > libraries
> > > > (mainly threading and OpenMP), so it makes sense to re-evaluate if
> > those
> > > > issues are solved form MinGW side before trying to support all the
> > > > libraries we need.
> > >
> > > i use mingw 4.72 with added openmp libs from here:
> > > http://tdm-gcc.tdragon.net/download
> > > and threading works properly no crashes, at least in my workflow.
> > >
> > >
> > > Regards
> > > Yousef Harfoush
> > > bat3a at msn.com
> > >
> > >
> > >
> > >
> > > >
> > > > On Sat, Dec 26, 2015 at 10:38 PM, alekulyn <alekulyn at gmail.com> wrote:
> > > >
> > > > > I talked to psyfi over IRC around half a year ago and told him I'd
> > like
> > > > > to help with this.  There have been several complications along the
> > > way,
> > > > > such as which MinGW version we should use, rumors that clang was
> > coming
> > > > > into the picture, and general inactivity regarding anything MinGW.
> > > > >
> > > > > As for which MinGW version to use, my conversation with psyfi was
> > > mainly
> > > > > about adding libraries to the mingw64_gcc49 branch he started.  To
> > that
> > > > > end, I did compile some libraries with MinGW-W64 GCC 4.9, but I must
> > > > > have deleted them some time ago.
> > > > >
> > > > > Anyway, like I told psyfi, I'm willing to help with this.  Just need
> > to
> > > > > know which MinGW version to use.
> > > > >
> > > > > On 12/26/2015 5:12 PM, Sergey Sharybin wrote:
> > > > > > Hey everyone,
> > > > > >
> > > > > > There are some missing precompiled libraries (sndfile, opensubdiv,
> > > OSL)
> > > > > and
> > > > > > some misng libraries update (python, SDL, OpenAL)  for MinGW.
> > > > > >
> > > > > > This makes MinGW builds quite diverged from the official builds
> > > > > feature-set
> > > > > > and lib-version wise, moving MinGW builds to the boundary where we
> > > can't
> > > > > > call it officially supported anymore.
> > > > > >
> > > > > > Additioanlly, svn:externals for mingw folders seems to be
> > > misconfigured
> > > > > now
> > > > > > and needs clean up.
> > > > > >
> > > > > > Anyone to have a look and fix all those issues?
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Bf-committers mailing list
> > > > > Bf-committers at blender.org
> > > > > http://lists.blender.org/mailman/listinfo/bf-committers
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > With best regards, Sergey Sharybin
> > > > _______________________________________________
> > > > Bf-committers mailing list
> > > > Bf-committers at blender.org
> > > > http://lists.blender.org/mailman/listinfo/bf-committers
> > >
> > > _______________________________________________
> > > Bf-committers mailing list
> > > Bf-committers at blender.org
> > > http://lists.blender.org/mailman/listinfo/bf-committers
> > >
> >
> >
> >
> > --
> > With best regards, Sergey Sharybin
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers