[waffle] [GSOC 2014] How to deal with non win32 api, wgl(Create, Make)Context depends on existing window

Chad Versace chad.versace at linux.intel.com
Thu Jun 5 10:00:27 PDT 2014


On Wed, Jun 04, 2014 at 11:47:32PM -0700, Jose Fonseca wrote:

> > I thought we wanted to go ahead an provide a binary build for windows, and
> > thus:
> > 1. It should be buildable under Linux using mingw
> > 2. The binary should have a reasonable license situation
> >
> > Didn't we already pretty much have this worked out anyhow?
> 
> Maybe I misinterpreted things.  I always saw mingw as a mean to an end, to facilitate development and get things started (ie, without forcing Emil to obtain and learn to use use a completely new set of tools).  And not the end itself (distribute binaries to the world), because:
> 
>  - MinGW often generates bad code, I've seen it happening with Mesa and Apitrace [1]; so I while use MinGW debug binaries all the time, I don't trust MinGW to produce distributable release binaries
>  - MinGW debug information is not understood by MSVC tools, so when an MSVC user debugs its code, it won't be able to get any symbols from waffle if waffle was build with MinGW
> 
> IMHO, the best sort of binaries are .DLLs produced by MSVC (any version) with statically linked CRT (so no additional dependencies -- no need to ship MSVC redistributables installer).  And they should be usable with applications built with anything (MSVC MinGW)  
> 
> Anyway, this is just a mere suggestion.  I can always build my own binaries from source if needed.

Jose, I had the same interpretation as you. Despite being useful for
development, mingw was a mean to an end.


More information about the waffle mailing list