Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <001e01c2d78c$e59ead50$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Ben Clewett" <B DOT Clewett AT roadrunner DOT uk DOT com>
Cc: <cygwin AT cygwin DOT com>
References: <F37KT2qeSqk0qcITzSO00000d4d AT hotmail DOT com> <3E525380 DOT 2000801 AT roadrunner DOT uk DOT com>
Subject: Re: Duplicate CygWin
Date: Tue, 18 Feb 2003 20:32:46 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Ben Clewett wrote:
> For my working, I would need a fully detached CygWin.  It's own
> memory, it's own DLL, and not a dependence on an existing
> installation.
>
> This is because I will be using Install Sheild to load and run an
> entire application, which is compiled under CygWin, onto a foreign
> machine, which may be of any setup including an old, badly setup,
> hached and conflicting CygWin...  Also then the 'Add/Remove Software'
> can rid the foreign OS of my stuff, without deleting the CygWin which
> is being used by my poor customer.
>
> I do not need this for about six months, so will give me plenty of
> time to have a good hack and get to know CygWin a lot better....

Make sure you aware of licensing issues before you start bundling the Cygwin
DLL with something.

On the technical side, I have been able to prepare an isolated Cygwin - I
now have a mygwin1.dll and a simple "Hello World!" exe that uses it, and
which does not clash with running cygwin.

I would like to point out that there was one stumbling block in addition to
DLL name and shared memory ID. It is only an issue if you want to run a
mygwin exe from a cygwin one. It is the child_info struct that it passed
between cygwin processes. Currently, you get version clash here, requiring
some hacking to enforce isolation here too.


Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/