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
c
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 th
Hi Thomas, I can't really see what is the problem, since MinGW
libraries usually use the lib.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
Hi,
Think i'm one from guys who's responsible for gcc libs. But i can't see why
we need to use different png libs for mingw and msvc.
Basically, only libraries which are using C++ should be definitely split,
but if C++ isn't used in libs it should be possible to use them in both of
mcvc and gcc.
Hey,
I would like to move *all* mingw libs to lib/windows/gcc. There are some
libs already, but some are still inside the "normal" directories.
This is bad as it makes it harder for the msvc maintainers to upgrade libs.
I just updated the png libs, but in the same dir are the mingw libs.
I want
