X-Spam-Check-By: sourceware.org Date: Tue, 23 Jan 2007 09:32:03 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Questions about porting from Linux to Windows... Message-ID: <20070123083203.GD27843@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20070122175919 DOT GA27843 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jan 23 00:28, jano trouba wrote: > In the examples you gave me of different applications (Hello), they are > both LINKED via cgwin. Yes, but the results are different. When using the -mno-cygwin flag your build native Windows applications, when not using that flag you build Cygwin applications. > [...] > builder using static ".a" libraries compiled with the cygwin environment, > with the -mwindow flag... ^^^^^^^^ See below > So if I understood correctly what you told me in your last message, if I > follow the above-mentioned procedure I should be in the clear both in the > licensing side (not needing any licence fee) and in the runtime side (not > needing cygwin DLL) (the libraries should contain WIN32 code). > > Is this correct ?? No. You have to use the -mno-cygwin flag. With just the -mwindows flag you still create Cygwin code if the -mno-cygwin flag is not used. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/