🚀 go-pugleaf

In article <92Apr10.183524edt.144354@explorer.dgp.toronto.edu>, jinli@dgp.toronto.edu (Jin Tonic Li) writes:
|> 
|> I am porting a windows app written with MSC 6.0 and SDK 3.0 to BC++ 2.0
|> The C source codes compiled fine with minor changes to associate function
|> prototypes with each individual module vs putting all of them in one 
|> .h file and include it in all module files.
|> 
|> However, the linker gives warning about exporting dialog functions:
|> 
|> 	Attempt to export non-public symbol XXXXX
|> 
|> where XXXXX is the name of the dialog function.  The dialogs are called
|> through MakeProcInstance(XXXXX, hInst) which are all listed under
|> EXPORTS in .def file.
|> 
|> I have tried the options All windows functions exportable and Explicit
|> export for BC++ 2.0  The linker still gives the same warning.
|> 

Try removing the export statements from the .DEF file, and keep the _export
on the function declaration in your code.  Remember, C++ does name mangling.

jim mullens
mullens@jamsun.ic.ornl.gov (128.219.64.31)
voice: 615-574-5564