- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a library of routines from which I create an object library (.lib) and a DLL (.dll).
I currently use a custom pre-processor which removes the "!DEC$ATTRIBUTES DLLEXPORT :: name" statements, (and one or two other DLL-specific statements), when I am compiling for the object library.
I am wondering if I can avoid using a pre-processor.
Would it matter if I left the "!DEC$ATTRIBUTES DLLEXPORT :: name" statements in when compiling for the object library?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having DLLEXPORT directives in code not built into a DLL is "mostly harmless". The code will work fine, but the linker will create an export library when the executable is linked, which may be annoying.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could use module definition files or command line options to specify the procedures to export, as an alternative to DLLEXPORT directives.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page