Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com X-Authentication-Warning: sequoia.cs.berkeley.edu: maratb set sender to maratb@CS.Berkeley.EDU using -f To: cygwin@sourceware.cygnus.com Cc: abegel@cs.Berkeley.EDU Subject: problems linking g++-generated dlls with VC++ applications From: Marat Boshernitsan Date: 01 May 2000 19:58:30 -0700 Message-ID: Lines: 17 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Biscayne) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii I have a C++ application in Visual C++ that I need to link with a C++ dll that is compiled with g++ (is this even possible?). The application only uses extern "C" functions of the dll, so the name mangling differences are not an issue. What is an issue, however, is that the dll has some global objects whose initialization does not happen when the dll is loaded (I built a small testcase to verify that) by the VC++ application, whereas g++/cygwin applications that link against the this dll are fine. Is this a bug, or a known misfeature? Any suggestions or workarounds? Do I need to do anything special in DllMain? Can I make some explicit calls to ensure proper initialization? Thanks in advance, Marat. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com