|Mailing List firstname.lastname@example.org Archived Message #5
Yes, the first part of the compile involves generating quite a few hhSome of these .idl files, such as wpdataf.idl, are part of the toolkit as
files out of idl files.
is wpdataf.h and wpdataf.xh. Others such as wpdataf.hh are not, so you
need to generate them if your code needs them and it appears the cwmm
does. The .hh files are used by code that uses the DTS interface. See
the SOM Programming Guide in the toolkit for the details.
No sign of progfolder*Perhaps this one got lost. For now, comment anything that requires it out
of the build, which means don't build progfldr.dll/progfolder.dll.
and wpdataf.hh seems toIt's not.
be a system header
as it is surrounded by <> and the only wpdataf.*wpdataf.h is provided by the toolkit, so it can be considered a system
files I find are in the toolkit and no hh file.
header. Keep in mind that the only thing that <> does is change the
include search order. Whether or not a file is system header is somewhat
a matter of POV.
The lack of a wpdataf.hh is not a problem because none of the code
requires it, which explains why the make files don't create it.
All but those 2 are generated. I assume that progfolder.hh should beWe need to track down progfolder.idl, but that can happen in parallel with
generated from progfolder.idl or be referenced somewhere other then an
include line in the source.
getting everything else to build.
You might try turning off optimization and see if that works around the
E-post til ListMaster