- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am in the early stages of converting a large multimodule Win32 program from CVF to IVF (just downloaded 8.1).
One of the solution projects is a DLL containing dialog resources & definitions. The compiler creates the .DLL output just fine, but never creates the companion .LIB output file. (This worked perfectly in CVF/DevStudio).
In VS, the project Properties->Linker->Advanced has the correct entry for the import library filename to be created. What else needs to be done in order for the output .LIB file to actually be created?
TIA, Paul Curtis
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the linker does not see any symbols exported, it does not create the export .lib. Do you have a .DEF file that names the symbols to be exported?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CVF exported a .lib without a .def file, but IVF seems to require one. I used the various root.def samples supplied with IVF to create the simplest .def file, and the .lib output was then created. Should the creation of missing .def files be part of the automatic conversion feature? Not a big deal, though. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am puzzled as to how this worked with CVF, if what you have are resources and not routines. The project converter would not know how to figure out what you were doing here. Using a .DEF file is the appropriate solution.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page