Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id:	<199906280258.VAA23658@mercury.xraylith.wisc.edu>
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	running two independent Cygwin DLLs?
Date:	Sun, 27 Jun 1999 21:58:15 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

I need to get a setup where I'm running two perhaps incompatible Cygwin
DLLs, and wondering if that makes any sense at all. This is what I've
done:
  - have stock Cygwin dll etc running everything including remote access
    (that's why I can't just replace the current one etc)
  - modify the 2nd one (this is a new snapshot) to 
    * have a different name, say cygwin1-test.dll, and regenerate the
      import library accordingly, so that the newly linked apps will 
      refer to this instead.
    * change the shared address and name so that the new DLL won't
      see the values for the stock one.

Would this work, or am I fooling myself? I can see some potential
pitfalls such as mount table issues, but is there something fatal
waiting to happen?

Regards,
Mumit

- Raw text -