Hi Steven
We've (ReactOS) already gone beyond the header issue with the
decision to do a vendor branch of WINE. With regards to doing the
same for ZLib and FreeType: well spotted! We should definitely do the
same there.
As I understand it, with a vendor import of WINE it doesn't matter to
us (Rea
From: "Jason Filby"
> The only thing that worries me is Danny saying that they're not
> aiming for the Windows SDK/DDK! If this is true then we may have to
> keep our own headers, public or otherwise?
>
Small correction. I don't know what "they" are aiming for. I only know
what I am aiming for -
Ok thanks for clearing that up. Since our priority is SDK/DDK we'll
probably be the main submitters of such code then.
Regards
Jason
--- Danny Smith <[EMAIL PROTECTED]> wrote:
> From: "Jason Filby"
> > The only thing that worries me is Danny saying that they're not
> > aiming for the Windows SDK/
Hey Danny,
--- Danny Smith <[EMAIL PROTECTED]> wrote:
> Small correction. I don't know what "they" are aiming for. I only
> know
> what I am aiming for -- and that is to provide a good, affordable
> compiler toolset for the ordinary user. The SDK/DDK is a low
> priority
> for me personally. Rig
This is really the heart of the issue. Can we work out a system that
will work for all projects involved? What I am about to bring up is not
the same issues that Danny has with GCCisms but it has made me think
about our build system again.
WINE and Mingw both make use of some of the aspects of the
