No, the linkage convention for your DLL shouldn't make a difference unless the log4cxx library is not included. I built a DLL accessed by Smalltalk just fine, but the log4cxx classes (0.9.7, I'm afraid) were included in my special DLL rather than being a separate DLL.
Have you specified the log4cxx library as input to your DLL build? Cheers! Tom Hawker Home 408-274-4128 Office 408-576-6591 Mobile 408-835-3643 -----Original Message----- From: Vijai Kalyan [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 16, 2005 08:08 PM To: [email protected] Subject: Unresolved Externals when calling logging methods from extern "C" function. Hello, I am writing a dynamic library that needs to have its exported functions declared with the C calling convention. I am getting unresolved externals for the log4cxx methods/functions which are used in these functions. The unresolved symbols seem to be mangled names which is why I am posing this question: Is my problem really due to the calling convention? thanks, -vijai. IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in so doing. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com.
