Congradulations - windef.h
julliard at winehq.org
Thu Jan 1 19:43:52 CST 2004
Boaz Harrosh <boaz at hishome.net> writes:
> Conclusion: winegcc should stick to command-line switches and
> translations of options. like include directories, extra libs and so
> on. All code related and defines should go to an header file. If you
> don't like the ms-extensions.h name than it can be winegcc.h.
It's not the name, it's the fact that we add a header that doesn't
exist on Windows. You still haven't answered the real question: why
wouldn't it work to have them in winegcc?
julliard at winehq.com
More information about the wine-devel