standards for building
Thu Dec 16 10:27:00 GMT 1999
--- John Huddleston <firstname.lastname@example.org> 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
> 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 email@example.com should still work.
Aren't changes fun? ;^)
Earnie Boyd < mailto:firstname.lastname@example.org >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
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 email@example.com
More information about the Cygwin