From: Robert K. <ro...@ko...> - 2002-05-29 18:53:32
|
I think keeping wine is superfluous. We'd rather establish a dynamic import and patch process. What about the OS2 sub system? It'll get its own module- OK. Who will do this? When? What will be the name? How can I reach it? Is it still CVS? Shall I establish my own build process? Casper Hornstrup schrieb: > ons, 2002-05-29 kl. 02:33 skrev Steven Edwards: > > So what is the final outline for strucure of our cvs tree? This is the > > way I think we have it but I want to double check. This is by no means a > > compleate outline. > > > > CVSROOT - > > -win32 (wine tree + certain moved reactos/lib modules) > > -include > > -dlls > > -tools > > -programs > > ? > > > > Thanks > > Steven > > Are we keeping WINE in our CVS? When WINE compiles with MinGW, we really > don't need to have any ReactOS specific modifications to it, so it would > be better to checkout a copy of WINE from the WINE CVS instead. Then > there is no need to synchronize two modules. > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel |