delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
Subject: | RE: Building for nocygwin |
Date: | Mon, 23 Apr 2012 16:52:54 +0200 |
Message-ID: | <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D01E@bespdc01.mediaxim.local> |
In-Reply-To: | <20120423140440.GG7097@calimero.vinschen.de> |
References: | <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFD0 AT bespdc01 DOT mediaxim DOT local> <CA+sc5m=cKU5DaZFeJuEas-nfXD9uAsxq4V_9hcoUAM77u3OKNA AT mail DOT gmail DOT com> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEF AT bespdc01 DOT mediaxim DOT local> <CA+sc5m=mC16bBFTBpPACoewcxKWt4KSsH22mUiVu0BrYCVObyQ AT mail DOT gmail DOT com> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D004 AT bespdc01 DOT mediaxim DOT local> <20120423140440 DOT GG7097 AT calimero DOT vinschen DOT de> |
From: | "Michel Bardiaux" <MBardiaux AT mediaxim DOT be> |
To: | <cygwin AT cygwin DOT com> |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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 |
X-MIME-Autoconverted: | from base64 to 8bit by delorie.com id q3NErcAj023970 |
> As Earnie wrote, now you should use the appropriate mingw32 or mingw64 cross compiler, > both of which are available as part of the Cygwin distro. > This *is* the general solution. I *get* that. My problem was, the web is so cluttered with pages mentioning the no-cygwin thing (including the cygwin FAQ!) that finding a good howto is nearly impossible. Lots of pages about running the mingw toolchain on mingw/msys, but at some point in the past I had installed cygwin *and* msys, and managing the path, the profile scripts, etc was a real pain, so never again. With the benefit of Csaba's hint, the basic recipe is now: 1. Install mingw-gcc-core (which pulls other necessary packages) 2. i686-pc-mingw32-gcc -o jef.exe jef.c With that under my belt, I can start thinking about adding spices, herbs, truffles, and soy sauce :-) Is there a deep reason not to amend the FAQ?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |