On Fri Mar 20 09:47:23 2026 +0000, Jacek Caban wrote:
Yes, it's about those two extensions mostly. I could maybe disable others, but why? They are well handled by make_opengl. I also don't see how being similar to other extensions changes anything. The issue I see is that exposing extensions that aren't expected to be there by applications have a chance of confusing them. It's possible for instance that an application check for GL_ANGLE extension and decide to enable some ANGLE specific rendering mode. On Windows the AMD drivers do not support those extensions, but on Wine most of the time Mesa is used for AMD GPUs and they would be exposed.
The same logic applies to platform specific extensions like GL_APPLE or other platform extensions that are currently filtered out. Sure `make_opengl` could support some of them, and sure, GL extensions aren't restricted and some other driver could implement them including on Windows, but it's not the case in practice and passing them through creates a runtime environment that differ from any possible native environment Windows applications have been developed for. Filtering out extensions which aren't, or very rarely, there on Windows is less likely to break anything, because no application is expected to benefit from them anyway. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133536