delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/05/13/19:39:30

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: <012e01c319a8$ca760c40$6400a8c0@FoxtrotTech0001>
From: "Bill C. Riemers" <cygwin AT docbill DOT net>
To: <cygwin AT cygwin DOT com>
Subject: Help cross compiling for MingW32 standalone executables.
Date: Tue, 13 May 2003 19:35:40 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

I've been attempting to build mingw32 standalone executables by cross
compiling with the -mno-cygwin option.  I thought it was working correctly,
until I handed off the execuables to someone without cygwin.  It turns out
the executables still link in cygwin1.dll.  Does anyone know what flag I
should use to get a true standalone excutable?

                                            Bill



--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019