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: <A7E3A4B51615D511BCB6009027D0D18C05F1D677@aspams01.ca.com>
From: "Reddie, Steven" <Steven DOT Reddie AT ca DOT com>
To: cygwin AT cygwin DOT com
Subject: gcc2cl
Date: Fri, 23 Aug 2002 16:42:27 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

I'm writing a utility to translate a gcc command-line to an MSVC
command-line and then spawn MSVC's cl.exe.  It started life as a script
which I developed for configuring and building OpenSSL and OpenLDAP with
CC=gcc2cl.  It does things like force object extensions to .o, search -L
paths for -l libraries (libxxx.a, libxxx.lib, xxx.a, xxx.lib) and specify
them properly, dos2unix stdout/stderr, and filter out the source filename
from stdout/stderr that MSVC displays while compiling.  This makes it work
with autoconf as used by OpenLDAP.  I figure this may be generally useful.
Is it something that should go in the Cygwin distribution?  If so, how do I
go about contributing it?  I'd like to finish it off a bit more before
handing it over, and I will probably also do an ar2lib, and maybe an ld2link
if it proves necessary.

Regards,

Steven
--
Steven Reddie <Steven DOT Reddie AT ca DOT com>
Senior Software Engineer
Computer Associates Pty Ltd (Australia)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/