Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<3.0.1.32.19990422212138.0068ae60@pop.iperbole.bologna.it>
X-Sender:	vaf9143 AT pop DOT iperbole DOT bologna DOT it
X-Mailer:	Windows Eudora Light Version 3.0.1 (32)
Date:	Thu, 22 Apr 1999 21:21:38 +0200
To:	cygwin AT sourceware DOT cygnus DOT com
From:	Glauco Masotti <vaf9143 AT madrona-a DOT iperbole DOT bologna DOT it>
Subject:	part 3: mixing GNU and MS tools/libraries...
Mime-Version:	1.0

Hello. Maybe the title of this post is no more appropriate now.
I finally succeded in building a dll after converting the library (me10f.lib)
in libme10f.a and following the examples by Mumit. I wrote a DllMain
which does some initializations I need at attach time. However I am not able
to get ME10 load the module. I supposed that my case is "loading a dll by a 
non-cygwin app" right? Well if I provide the entry point at 
__cygwin_noncygwin_dll_entry AT 12 ME10 shuts down as soon as it has loaded 
the module. Otherwise if I let dllwrap define the default entry point
the program tells "I am loading the module tnt.dll" and hangs.
Can anybody guess what's going on and tell me?
I tried to make things simple and I am now working with a very simple
test case (a dll which makes an arc thru 3 points) to concentrate just on
the process of building the dll using GNU tools and let ME10 load it.
BTW this is an example which takes few seconds to be built using MS tools,
so I am quite bewildered about the intrinsic reasons which make the process
so complicated following "the other way". Nevertheless I would be very happy
to get to the end following this way, because of all the Unix/X based code
which otherwise would require extensive rewriting.
Regards.
--- Glauco Masotti





--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -