H
hector santos
Guest
There are really two issues here:
1) Is there a IDE "template/macro" way for separating MIDL generated stub client/server files and within multiple configurations?
In my solution, I have 3 RPC server APIs that creates 3 server side stubs and 3 client stubs and 4 headers files!! 6 dlls created!
The problem is that the stub *.c file names are the same for each of 4 configurations, so this really throws off the make system when one configuration alters the stubs, forcing a new compile and link conflicts among the projects, which leads to another issue:
2) A RPC client dll is dependent on the RPC server dll which is dependent on the IDL file. However, the IDE does not allow you to create a dependency for the IDL file.
Examples:
Compiling the wcsrpc.idl with MIDL creates the default file names:
wcsrpc.h
wcsrpc_s.c
wcsrpc_c.c
Same with wrgate.idl and wrmw.idl, creates:
wrgate.h
wrgate_c.c
wrgate_s.c
wrmw.h
wrmw_c.c
wrmw_s.c
I don't know, but me thinks since they are auto-created, the IDE/compiler should have it in a configuration target folder.
The problem is you can't single source the project files. Maybe the MIDL IDL properties can allow you to use macros for the Header, Client and Stub file name fields (haven't tried it), but you can't do this in the IDE source tree. You would have to include all the *.c files and then exclude the different file compiles per configuration.
No? Easier way?
Hector Santos, CTO Santronics Software, Inc. Santronics Software, Inc.
Continue reading...
1) Is there a IDE "template/macro" way for separating MIDL generated stub client/server files and within multiple configurations?
In my solution, I have 3 RPC server APIs that creates 3 server side stubs and 3 client stubs and 4 headers files!! 6 dlls created!
The problem is that the stub *.c file names are the same for each of 4 configurations, so this really throws off the make system when one configuration alters the stubs, forcing a new compile and link conflicts among the projects, which leads to another issue:
2) A RPC client dll is dependent on the RPC server dll which is dependent on the IDL file. However, the IDE does not allow you to create a dependency for the IDL file.
Examples:
Compiling the wcsrpc.idl with MIDL creates the default file names:
wcsrpc.h
wcsrpc_s.c
wcsrpc_c.c
Same with wrgate.idl and wrmw.idl, creates:
wrgate.h
wrgate_c.c
wrgate_s.c
wrmw.h
wrmw_c.c
wrmw_s.c
I don't know, but me thinks since they are auto-created, the IDE/compiler should have it in a configuration target folder.
The problem is you can't single source the project files. Maybe the MIDL IDL properties can allow you to use macros for the Header, Client and Stub file name fields (haven't tried it), but you can't do this in the IDE source tree. You would have to include all the *.c files and then exclude the different file compiles per configuration.
No? Easier way?
Hector Santos, CTO Santronics Software, Inc. Santronics Software, Inc.
Continue reading...