Thread: module definition file

Hello everyone,


I am using Visual Studio 2005 to develop C++ DLL (in-process COM). There is a setting in Linker --> Input called Module definition file. This setting makes me confused,

1. I have tried that if input a file name (.def), then the generated DLL be larger than the time when we leave the module definition file to empty. Should we leave it empty or non-empty (input a .def file name);

2. What is the function of the module definition file? Should developer write it manually or generated by system.


thanks in advance,
George

Hi hk_mp5kpdw,


After reading the help information and also some resources in MSDN, I am confused.

http://msdn2.microsoft.com/en-us/lib...5y(VS.80).aspx

Originally Posted by hk_mp5kpdw

Highlight the "Module Definition File" line in the property page for your project and click on the "?" in the upper right hand corner to get help on that item.

Previously I always use import library files (.lib) as linker input of the application if I need to make my application dependent on a DLL, seems we can replace the import library file (.lib) with .DEF files?

I am interested to learn from you. Could you show me some steps in Visual Studio? I am using Visual Studio 2005, but if you are using other versions, it is ok.


regards,
George

1. Should we leave it empty or non-empty (input a .def file name);

Use a .def file if that's your preferred method to export identifiers to make them visible by applications using your dll.

2. What is the function of the module definition file? Should developer write it manually or generated by system.

There is a wizard but only for mfc-dll's iirc. else you have to write them manually. its not that hard. you have to create a .map file first, which lists all c++ function names. than you are able to map that inside your .def file.
look up the msdn, its pretty well explained there.