Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<004d01bf47bd$a6adeaf0$426a4fa2@itc.nrcs.usda.gov>
From:	"John Huddleston" <jhuddles AT rocky DOT itc DOT nrcs DOT usda DOT gov>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	standards for building
Date:	Thu, 16 Dec 1999 05:04:05 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300

To Cygwin group,

I have used Cygnus B20.1 to compile an older version
of GRASS for an application that we use.  Everything
went OK but I did have to hack in some changes in
the Makefiles, the Gmakefiles, and the source.

Someone from the GRASS organization contacted me
and asked me to build their most recent 5.0beta6a.
That's fine; however, I wanted to make the "hacks"
consistent with your standards for building CygWin
compliant products.  For instance, would I use a
"#ifdef Cygnus" to isolate source code?   What
would I use in the makefiles?

BTW, we are moving behind a firewall soon so I will
have to unsubscribe and re-subscribe to this list.  The
id jhuddleston AT itc DOT nrcs DOT usda DOT gov should still work.

John Huddleston



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -