Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: setup changes to build standalone MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 26 Apr 2002 15:51:40 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Robert Collins" , "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3Q5qVG31040 > -----Original Message----- > From: Robert Collins > Sent: Friday, April 26, 2002 3:28 PM > To: Robert Collins; Cygwin-Apps > Subject: RE: setup changes to build standalone > > > > > > -----Original Message----- > > From: Robert Collins > > Sent: Friday, April 26, 2002 1:03 PM > > To: Cygwin-Apps > > Subject: setup changes to build standalone > > > > > > To build setup we need: > > a mingw bz2lib > > a mingw zlib > and a mingw getopt. For now I'm putting this in the setup > directory, but I'll almost certainly bundle it with > libgetopt++ (as no symbols from it are needed by the setup sources). sigh. And /src/winsup/cygwin/include/cygwin/version.h and /src/winsup/cygwin/include/sys/mount.h. For starters I'm just absorbing the content (only mount.cc needs them). However I think we should look at either a) having a mingw library for manipulating cygwin mount points officially available or b) having setup.exe call cygwin's mount.exe to setup the mount points in the first place, rather than setup being tightly linked to cygwin's registry format. c) some variation on the above themes. d) a --with-cygwin-headers=/path/to/headers and in mount.cc pickup the needed headers. Rob