Bob Rossi wrote:
> Nice, I was wondering how you could develop on Cygwin without this
> capability. That makes perfect sense. I'm just guessing, but it might be
> a good idea to make this hardcoded constants dynamic, so that any
> arbitrary number of cygwin1.dll's can coexist.
I can imagine that it should be possible for someone relatively familiar
with the cygwin build system to write in a few hours a patch that would
parameterize this, so that you could do something like
./configure --with-shared-id=foobar \
--with-mount-table-id=foobar --with-dllname=foobar
and end up with a "cygfoobar1.dll" that uses "foobar" in the shared
memory region name and registry mount keys. Then (using the proper gcc
parameters) you could compile your package to use this cygfoobar1.dll
and have no dependence on cygwin1.dll, and be completely isolated from
any existing cygwin on a system.
Of course, nobody associated with Cygwin would then want anything to do
with trying to support such a frankensteined installation. And it's not
clear to me that such a patch would even be accepted. But it should be
relatively easy.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
