Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sat, 1 Dec 2001 22:10:05 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: problem with cygwin version 1.3.4 cross compilation using gcc Message-ID: <20011202031005.GA20417@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00ab01c17ad3$03d6c720$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00ab01c17ad3$03d6c720$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Sun, Dec 02, 2001 at 12:45:25PM +1100, Robert Collins wrote: > >=== >----- Original Message ----- >From: "Rahul" >To: "Robert Collins" ; > >Sent: Sunday, December 02, 2001 10:47 AM >Subject: RE: problem with cygwin version 1.3.4 cross compilation using >gcc > > >> Hi, >> >> <<>>>> >> >>Thanks for responding. I was of the opinion that once I have >>binary/exe I just need cygwin1.dll. This is what impression I get at >>most of the cygwin website. It sound very odd that for distributing a >>software that we make using cygwin, we need to have complete cygwin set >>up on client's machine. Can we have some workaround to this ? > >Eric's more detailed answer address's this. You don't need all the >utilities and so forth that are available, but you *DO* need the path >and mount table setup correctly. You could just use the appropriate UNIX function, aka mount(), to mount the cygwin root in a program. You don't have to install a cygwin distribution to manipulate the mount table. cgf -- 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/