|
Archives
D Programming
digitalmars.Ddigitalmars.D.bugs digitalmars.D.dtl digitalmars.D.ide digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger D.gnu D C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript electronics |
c++.command-line - Exporting symbols from an executable with optlink
Is there a way to perform back linking with OPTLINK? What I'm getting at is that I'd like my executable to export it's symbols so that DLLs loaded at runtime have access to them. I'll be linking DLLs at runtime with LoadLibrary() and the DLL code may have to access symbols in the executable. GNU ld has an option "--export-dynamic" which tells the linker to export all symbols of the executable so they can be seen by dynamic libraries loaded at runtime. Other linkers I've used, in particular Solaris ld, always perform exporting of symbols by default. Is this how OPTLINK works? Is there an equivalent switch to "--export-dynamic" available with OPTLINK? Thanks for the help, Michael Feb 18 2004
Michael wrote:Is there a way to perform back linking with OPTLINK? What I'm getting at is that I'd like my executable to export it's symbols so that DLLs loaded at runtime have access to them. I'll be linking DLLs at runtime with LoadLibrary() and the DLL code may have to access symbols in the executable. GNU ld has an option "--export-dynamic" which tells the linker to export all symbols of the executable so they can be seen by dynamic libraries loaded at runtime. Other linkers I've used, in particular Solaris ld, always perform exporting of symbols by default. Is this how OPTLINK works? Is there an equivalent switch to "--export-dynamic" available with OPTLINK? Feb 18 2004
|