Home |
RTTarget-32 Programming Manual Running Win32 Programs without Win32 Running a Program on the Target Running with or without Paging Installing Hardware Interrupt Handlers Catching NULL Pointer Assignments Running without Run-Time System Configuration for Debug and Release Builds Linking Rtt32.lib into the EXE Using Microsoft Run-Time System DLLs Loading DLLs through a File System Using the MetaWINDOW Graphics Library Custom MP Floating Pointer Structure Compiling and Linking with On Time RTOS-32 |
Linking Rtt32.lib into the EXEWhen Rtt32.lib is linked into the main program, other DLLs can access RTTarget-32's functions in the EXE if they are exported. This generally means that a module definition file has to be used when linking the EXE. The DEF file must list all functions (RTTarget native and Win32 emulation) needed by other modules with EXPORT directives. The advantage of this method is that only those parts of Rtt32.lib actually used by the application are linked. The disadvantage is that maintaining DEF files can be cumbersome. However, utility Makedef.exe can be used to automate DEF file maintenance (see section Utility MakeDef). RTLoc's Dynamic Link Report (which must be explicitly enabled with option -Rd+) in the .LOC file can be used to analyze exactly which functions must be exported. All missing functions will be reported in warning messages. If you have exported functions not required by the application, they will be listed under unreferenced entrypoints at the end of the Dynamic Link Report. Example program DLLDemo2 shows how to link Rtt32.lib and export RTTarget-32 functions to other DLLs.
|