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 Message-ID: <00ab01c17ad3$03d6c720$0200a8c0@lifelesswks> From: "Robert Collins" To: , References: Subject: Re: problem with cygwin version 1.3.4 cross compilation using gcc Date: Sun, 2 Dec 2001 12:45:25 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 02 Dec 2001 01:46:44.0741 (UTC) FILETIME=[3285EB50:01C17AD3] === ----- 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. Rob -- 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/