what I may not do
> (i.e. may I call external unix processes ? whats about fork() ?)
I can't speak for wine policies, but we (ReactOS) really like it when
the code is written in a very windows-like way - don't assume you're
running on unix, and it'll make it easier for us to use your work too.
-Vizzini
ution under some conditions, particularly
the ones you get in compiler products. You need to read and understand
the relevant licenses.
You should also talk to a lawyer; don't take my word for it.
-Vizzini
o, check Gary Nebbett's book for more
info.
-Vizzini
On Mon, 2004-02-02 at 16:14, Steven Edwards wrote:
> Hi Guys,
> --- Vizzini <[EMAIL PROTECTED]> wrote:
> > There was a very interesting question brought up on Saturday morning
> > by
> > one of the Wine guys (Mike perhaps?) regarding running ReactOS inside
> > L
pected, given the state of our code. I spoke from a prepared deck
(http://plasmic.com/~vizzini) for about 15 or 20 minutes, and then we
demonstrated various aspects of the system. Steven ran the
demonstrations, which included showing off Explorer, Windows XP Notepad,
and our installation system
this is a bug, can someone fix it?
>
> It's a bug in your headers, and it's not present in the Wine
> headers (one again, why aren't you guys using our headers?)
We're still working out a plan for sharing headers; unfortunately it's
not as easy as just using Wine's headers.
-Vizzini
strategy really is in porting some of the usable
code? We can, again, keep a locally-modified vesrion in CVS, if there
are major chunks of those libraries that can be used directly.
Also, how would wine feel about adding ReactOS-specific code with some
conditional compilation or something?
I do hate to fork code...
-Vizzini
ms like a pretty big departure from the Windows
architecture that we are trying to clone, but if it enables a high
degree of code re-use, it may be worth it.
-Vizzini
y on that
situation, we'll probalby just do a cvs vendor import of wine and
refresh it regularly.
Does this sound workable to everyone?
-Vizzini
