Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-Id: <199909161221.HAA06533@mercury.xraylith.wisc.edu> To: Thomas Kowatsch cc: Cygwin List Subject: Re: automatic relocation problem? (WAS: problem with 3rd party lib) In-Reply-To: Your message of "Thu, 16 Sep 1999 15:11:31 +0200." <37E0EC83.2BA19012@stest.ch> Date: Thu, 16 Sep 1999 07:21:41 -0500 From: Mumit Khan Thomas Kowatsch writes: > > I think my 3rd party library is using the MSVCRT runtime. Is thereany > way I can use this 3rd party lib then and cygwin? > There are times when it will work, and there are times when it won't. It's not a simple issue, believe me. > Is this a general problem that MSVC libraries are not usable? So > the 3rd party vendor has to support a cygwin version? That would be nice of course. Before you do anything further, please fix your DLL making process and *remove* the erroneous entry point. Never override the entry point for any DLL unless you really know what you're doing (and if you do, ignore the rest of the paragraph). The way to handle this is to simply supply your own DllMain that will be called automatically by the default entry point. In your case, just don't use the library supplied one (ie., don't provide one and the linker will pick up the one in the library) since you don't do anything special. Doing the above of course doesn't mean that this particular case is going to work of course! Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com