Re: odl or idl?
Well, it has to - ODL is a language for a type library only...
To OP: you can use #import on the type library generated from
your ODL file using the following modifiers:
#import "your.tlb" raw_native_types raw_interfaces_only raw_dispinterfaces
[no_namespace]
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Igor Tandetnik" <itandetnik@mvps.org> wrote in message
news:OYJXVWqhHHA.392@TK2MSFTNGP06.phx.gbl...
spforeman <google@sforeman.com> wrote:
The project with the odl file doesn't seem to work the same. I can
add the enum to the odl file and change the interface prototypes to
use the enum, but no .h files are being generated
The difference is not between ODL and IDL - you can change the file
extension to .idl and it will behave exactly the same way. The difference
is in the file structure.
The way MIDL compiler works, .h file is generated based on the
declarations _outside_ the library block. TLB is generated based on the
declarations inside the library block. The usual approach is to defined
all the interfaces (and structs and enums) outside the library block, then
mention them inside (usually as part of coclass statement). This way, you
would get them both in the header file and in TLB.
Your ODL file, I bet, defines everything inside a library block.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925