Aleksey Vaneev wrote:
jpommier wrote:I guess that also means that it will be no longer possible to use mingw to build plugins on windows since g++ is not using the msvc abi...
Yep, that's true it seems if you are using an old mingw built around GCC 3.4. However, MinGW.org is making some steps to get GCC 4 working. But they do not have a complete setup yet for that, but you can at least hope they get GCC 4 working (together with 64-bit compiler) sooner than later.
I've successfully built VST3 'again' sample using stable stock mingw (GCC3.4). Only a few (cca 3 if I remember) single line no-brain-needed patches in sdk headers were needed. The most complicated stuff was getting gdi+ to work with mingw, but its related to vstgui.sf, not to core vst3. I've no C4/N4, but plugin seemed to work well in vst3sdk plugin test host.
Side note: I personally don't understand this whole VST3/C++ ABI hystery; the only thing from C++ ABI which matters in VST3 world is binary layout of classes with virtual tables and multiple inheritance of pure virtual classes. This is nothing complicated and pretty stable in GCC world for pretty long time. C++ ABI is easy in this area. Troubles come with exceptions, RTTI etc., but none of these 'advanced C++' things are used in VST3 interface. The same can be said for c++ stdlib; its ABI does not matter, because AFAIK nothing from c++ stdlib is used in VST3 interface.