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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: setup - inilint & building on cygwin X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Sun, 5 May 2002 16:26:28 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g456QaN26319 Just an update: 1) inilint, the setup.ini validator is coming along. It can be enabled via --enable-inilint on the configure line. It doesn't do anything just yet though, but will build successfully. 2) I had a configure.in syntax error that was breaking on-cygwin builds. That has been corrected. In aid of 1), the io_streams code now dynamically registers the providers - ie file:// and cygfile://. Pavel - this will affect your patch (hopefully by making it simpler). I'm considering changing cygfile:// to be posixfile://, for clarity - what you do folk think? Anyway, back to inilint, I'll be adding a new file:// provider that uses the standard calls, so it should build on anything, and be constrained purely by the host system's path syntax. It may not have the full complement of remove/link etc available (for obvious reasons). The last step for inilint is a check-only IniDBBuilder class, and then we'll have the first setup.exe derived tool. Woohoo! Rob