Which version of gcc are you using? You can look at the symbol table
of your loadable module with nm and determine what symbols are in
there. When I first was writing modules for MacOS X, the compiler
used libtool for the linking and the compiler inserted the underscore
(_) on all function names--that's why DXEntry became _DXEntry as the
load symbol. Maybe that has now changed.
David
The short path here is because I am invoking dx from the command line, with:
dx -mdf ./FancyRibbon.mdf
I did also check to see if changing the LOADABLE line in the mdf
file to the complete full path would make a difference. I get the
same error message just with the complete path now instead of just
a relative path, i.e. that DX cannot find the entry point DXEntry in
the module.
Still think that another linker switch is needed to make DXEntry the
actual entry point for the module.
Thanks,
Norm
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
