Re: Move Wine internal headers

[Alexandre Julliard]

Vincent Béron  writes:
> winegcc doesn't include eg /usr/include, so the headers referencing
> internal ones (mostly OLE related) fail. I thought it was cleaner to
> move wine internal stuff than to break down the includedir variable in
> Makefile to get to the parent of /usr/include/wine, ie /usr/include.

OK, I see. I think the idea with winegcc at this point is that if you
install Wine in a non-standard directory, you have to specify the
include path yourself, just like you need to ensure the Wine tools are
in your PATH. Besides, this shouldn't be an issue once the standard
includes are fixed to no longer reference the wine/obj_* ones.

Move Wine internal headers

[Steven Edwards]

--- Alexandre Julliard  wrote:
> OK, I see. I think the idea with winegcc at this point is that if you
> install Wine in a non-standard directory, you have to specify the
> include path yourself, just like you need to ensure the Wine tools are
> in your PATH. Besides, this shouldn't be an issue once the standard
> includes are fixed to no longer reference the wine/obj_* ones.

I was also thinking about submitting a patch to move any of the *16 headers and internal headers
that dont exist in the PSDK to include/wine. Is this ok?

Thanks
Steven

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Move Wine internal headers

[Alexandre Julliard]

Steven Edwards  writes:
> I was also thinking about submitting a patch to move any of the *16 headers and internal headers
> that dont exist in the PSDK to include/wine. Is this ok?

The 16-bit headers should already be in include/wine; if we have
missed some then sure it's ok to move them. The internal headers will
be removed, and in the meantime I think it's best to keep them where
they are.