On Tue, Jan 18, 2005 at 11:23:45PM -0600, Rob Shearman wrote:
As you guessed before, you can change the ".idl.h" rule in "Make.rules.in" in the root wine directory. Do a find on *.idl to find the files that are parsed by widl.
? oh - of course.
it hadn't occurred to me to simply change the rule globally :)
do you have a simple client/server test program that i can compile up [under wine], check it works, then evaluate?
I have sent you a test program off-list as it's quite large. It only checks a few simple types at the moment, but it can easily be expanded to more. The .idl file included with it should give the IDL compiler a good work out though.
ack.
[sadly, phil has a .exe and .zip stripping email rule in place :) these non-windows people, i dunno...]
okay, so just to check: in the _wine_ source code, at present, the only usage of widl is to turn .idl into .h - is that right?
i'm trying to get a handle on where i can help, given that dceidl can generate both client and server-side stubs given a lovely .idl file.
AH - i know - one important question: do you _happen_ to know where i can obtain that "OSF-DCE <-> MSRPC" header file which contains stacks of #defines like:
#define rpc_mem_free RpcMemFree #define rpc_binding_handle_inq RpcBindingHandleInq
i certainly can't afford to do an automated conversion of all the function names and structs to the lovely microsoft convention because it would be a complete merging nightmare for three very similar but subtly worked on codebases.
l.