This is the mail archive of the cygwin-developers@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

running two independent Cygwin DLLs?


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]