Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <19991216182537.15054.qmail@web117.yahoomail.com> Date: Thu, 16 Dec 1999 10:25:37 -0800 (PST) From: Earnie Boyd Reply-To: earnie_boyd@yahoo.com Subject: Re: standards for building To: John Huddleston , cygwin@sourceware.cygnus.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- John Huddleston wrote: > 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? Hmm... No replys yet. This one I can answer, #ifdef __CYGWIN__ is the correct macro check. > What would I use in the makefiles? > Hmm... Don't know how to answer this. Suggestion is to take a look at the documentation for autoconf, automake and existing packages. > BTW, we are moving behind a firewall soon so I will > have to unsubscribe and re-subscribe to this list. The > id jhuddleston@itc.nrcs.usda.gov should still work. > Aren't changes fun? ;^) ===== Earnie Boyd Cygwin Newbies, please visit __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com