[Bf-committers] MinGW libs in windows x32 svn

[Sergey Sharybin]

I don;t think we need separation by msvc/mingw, it should be more like
separation by libs.
Some libs can't be compiled by mingw (e.g. python) and some can't be
compiled by msvc (e.g. ffmpeg). And if library doesn't use some special
stuff like C++, OpenMP or so i shouldn't be necessary no separate
compilation and separating libraries in svn will just lead to storing the
same libs twice.
If you want to upgrade some library, you migh just ask guys to test them
with mingw, but it sohuldn't be i want upgrade some lib for msvc but i
don't care about mingw aproach,

On Mon, Dec 19, 2011 at 10:03 PM, Thomas Dinges <blender at dingto.org> wrote:

> Hi,
> this is correct. The issue is that sometimes msvc/mingw also share the
> header files, which could cause problems if we have very new msvc libs
> but old mingw libs.
> My main wish is that the different teams (msvc/mingw/msvc2010) can
> update their libs separately without worrying about breaking the others
> or extra work.
>
> Thomas
>
> Am 19.12.2011 17:00, schrieb Antony Riakiotakis:
> > Hi Thomas, I can't really see what is the problem, since MinGW
> > libraries usually use the lib<name>.a naming so there are no name
> > clashes between msvc/mingw. Now, there was also a discussion about
> > making a separate directory for each of msvc08 msvc10 mingw so that
> > builders can download only the one needed. This rationale is
> > acceptable imo but it should be made to work(Any svn wizards to point
> > at how this can be done?)
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
>
>
> --
> Thomas Dinges
> Blender Developer, Artist and Musician
>
> www.dingto.org
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin