Hey Greg, --- "Gregory M. Turner" gmturner007@ameritech.net wrote:
Wine doesn't have LPC per se. If ReactOS does, I'd love to see their
implementation and talk to you all about stealing it :)
http://cvs.reactos.com/cvsweb.cgi/reactos/ntoskrnl/lpc/
Uhh... so in answer to your question, rpcrt4 and rpcss are designed to work together, and shouldn't have too many ugly dependencies (except that rpcrt4 has some ole32 deps for its ndr implementation). For the most part, they only use high-level Windows-y stuff found in kernel32; there may be a few unixisms/wineisms, of course, but compared to other dlls these should be trivial.
Yes there are a few but maybe Casper and I can get these cleaned before we branch.
My advice: just run the code and see what happens. So long as ROS has working named-pipes, and a few other kernel essentials like critical sections, string atoms, etc, it ought to "just work", deficiencies and all. Just test with "/Oi" midl-generated code, and stick to the supported transports (lpc, ironically, or named pipes), or you will get no love. AFAIK, the only snag you may encounter is if your ole diverges from that of wine.. if that
We really dont want to diverge at all. I have tested hacked binarys under ReactOS and its seemed to work fine but that his been running only simple apps that depended on rpcrt4 and ole32.
Thanks for your help. It doesnt sound like we will have a problem at all.
Thanks Steven
__________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/