Re: IDL help, argh argh argh
typedef's should be just fine, though I usually recommend
against using then in IDL for other reasons.
You need to include the _i.c file from the base IDL in
your source file list, or #include it in exactly one source
file. Same as the _i.c file from your dependent IDL file.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Jason S" <jmsachs@gmail.com> wrote in message
news:1169494376.308191.272550@m58g2000cwm.googlegroups.com...
Alexander Nickolov wrote:
Don't use explicit paths. Use additional include directories
in your project settings under the C/C++ - General tab.
OK, thanks.
Defining your structs etc in the base IDL should suffice.
They should be visible in your C++ source file provided
you include the header file generated from the dependent
IDL. That one has a #include for the header generated
from the base IDL.
What about typedefs? I couldn't figure out how to get a typedef in the
base IDL to be visible in my project's c++ files.
Finally (and most annoyingly), if I have IID's declared in my base IDL,
how do I get them to be visible in my project's C++ files? I get a
linker error because they don't show up in my project's _i.c file.