Function export problem when porting MSC code to BC 2.0

Thread View: comp.windows.ms.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Jin Tonic Li Fri, 10 Apr 1992 22:35

#298

Author: Jin Tonic Li
Date: Fri, 10 Apr 1992 22:35

32 lines
1755 bytes

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.

When I run the application in windows 3.0, some dialogs would come up
but don't function the way they are supposed to; other dialogs would
cause UAEs/system reboot.  This behaviour would indicate that the dialogs
are not properly exported and associated with the instance's data segment.

How would I export them properly under BC++ 2.0?

Thank you,


--
Jin Li                               (416) 978-6619  //  Gin & Tonic mix well
Dynamic Graphics Project, Dept. of Computer Science  \\
University of Toronto, Ontario, Canada   M5S 1A1     //
jinli@dgp.utoronto.ca          uunet!utai!dgp!jinli  \\    No bugs, no bucks

Re: Function export problem when porting MSC code to BC 2.0

#342

Author: James A. Mullens
Date: Mon, 13 Apr 1992 22:12

25 lines
1594 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads