On Tue, Jan 18, 2005 at 03:34:22PM -0600, Robert Shearman wrote: > Luke Kenneth Casson Leighton wrote: > > >On Tue, Jan 18, 2005 at 01:51:34PM -0600, Robert Shearman wrote: > > > > > >so - the DCOM code is in the ole32 directory, yes? > > > > > > Pretty much. We don't really have any code using the DCOM interfaces > yet, but we will probably have to soon.
tests? tests i notice: those are unit tests? > >so, can i ask you - where are the key usage points for widl? > >WIDL is entered into every single Makefile and unfortunately > >there is a .idl.h entry in every Makefile too. > > > > > > I'm not quite sure what you mean by "usage points." i.e. as in where is it used to generate .h files from .idl files, and where is it used [if used] to generate client_stub and server_stub code? naively, i am looking for the points where i can replace the usage of widl with dceidl - should i be? > We don't have > makefile support for widl client/server code generation yet, but I > wouldn't worry about that for the moment. okay. > The only RPC file we really > have in CVS is the DCOM file - the IOXIDReslover and IRemoteActivation > interfaces. sorry, i'm floundering around a bit, here. > I can send you MIDL generated code for any IDL you send me if you > require it. thanks. okay. i admit to being a little confused. do you have a simple client/server test program that i can compile up [under wine], check it works, then evaluate? or know where i can get one? ta, l. -- -- <a href="http://lkcl.net";>http://lkcl.net</a> --
