16 May
2008
16 May
'08
1:15 p.m.
On Fri, May 16, 2008 at 2:57 AM, gedmurphy <gedmurphy(a)gmail.com> wrote:
I have so far pulled the source and built it. I
decided to target the
successful run of Office 2003 on reactos as my goal. (I have no idea how
realistic this goal is, and perhaps it already runs successfully ?).
At this point, I need some pointers on how to go about the job. I have seen
hints that I need to take the code over from wine into reactos etc.
Do I need to run wine in debug mode and see all the win-api calls that
happen
and port those calls from wine into react-os ?
Is there a hand-holding documents which describes this ?
Not really, you need to get to know the MSI and RPC source code. I
expect most of the remaining bugs blocking installation fall in to
either a kernel issue related to the Mm and Cc overhaul or given some
of the recent crash reports, the ReactOS RPC server might not be
playing nice with Wine's implementation of DCOM. DCOM is black magic
to me, so I highly suggest targeting the Wine regression tests for
ole32, msi and friends first, get all of the winetests passing on
ReactOS and then try to install Office 2003. You are going to need to
bruteforce it and just focus on fixing one api failure in the tests at
a time. Keep in mind the Wine test code and implementation for these
dlls is mostly sane as the current WineAPI failure rate for win2003 is
only 8% so your most likely going to be fixing bugs at a much lower
level in ReactOS code. If you find a real bug in Wine, talk to us on
IRC before submitting patches to Wine.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo