epics/pcas
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

improved doc

Browse Source
This commit is contained in:
Jeff Hill
1998-03-02 22:17:40 +00:00
parent ae1a1dc7b8
commit 5bd1407214
2 changed files with 26 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/include/shareLib.h
View File

@@ -36,12 +36,24 @@
* #include <in_this_dll_but_not_implemented_here.h>
* #include <what_I_implement_here.h>
*
* The point is: define epicsExportSharedSymbols exacly and only
* The point is: define epicsExportSharedSymbols exactly and only
* right before you include the prototypes for what you implement!
* Then include shareLib.h again because this is where they get changed.
* This time the epicsShare... macros expand to
* "export this from the DLL that we are building". (again only on WIN32)
*
* NOTE:
* If what_I_implement_here.h includes header files for routines that
* are not implemented in the DLL, then you will need to force these
* header files to be included before setting epicsExportSharedSymbols,
* including shareLib.h, and including what_I_implement_here.h. Since
* all well written header files have "ifdef" guards against multiple inclusion
* this is only a matter of "preincluding" the headers for these DLL
* imports before epicsExportSharedSymbols is defined. This
* is admittedly a bit of a mess, but is fortunately only the concern of
* persons who are adding routines to a library, and will have no impact
* on persons using routines out of a library.
*
* 8-22-96 -kuk-
*/

14
src/libCom/misc/shareLib.h
View File

@@ -36,12 +36,24 @@
* #include <in_this_dll_but_not_implemented_here.h>
* #include <what_I_implement_here.h>
*
* The point is: define epicsExportSharedSymbols exacly and only
* The point is: define epicsExportSharedSymbols exactly and only
* right before you include the prototypes for what you implement!
* Then include shareLib.h again because this is where they get changed.
* This time the epicsShare... macros expand to
* "export this from the DLL that we are building". (again only on WIN32)
*
* NOTE:
* If what_I_implement_here.h includes header files for routines that
* are not implemented in the DLL, then you will need to force these
* header files to be included before setting epicsExportSharedSymbols,
* including shareLib.h, and including what_I_implement_here.h. Since
* all well written header files have "ifdef" guards against multiple inclusion
* this is only a matter of "preincluding" the headers for these DLL
* imports before epicsExportSharedSymbols is defined. This
* is admittedly a bit of a mess, but is fortunately only the concern of
* persons who are adding routines to a library, and will have no impact
* on persons using routines out of a library.
*
* 8-22-96 -kuk-
*/