Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 3 Jul 2000 13:17:00 -0400 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: include incompatibilities Message-ID: <20000703131700.A27809@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <200007031336 DOT PAA23582 AT mail DOT bln1 DOT siemens DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007031336.PAA23582@mail.bln1.siemens.de>; from towo@computer.org on Mon, Jul 03, 2000 at 03:36:35PM +0200 On Mon, Jul 03, 2000 at 03:36:35PM +0200, towo AT computer DOT org wrote: >Chris Faylor also said: >: You're talking about normal problems with porting software between various >: systems. This kind of thing is a fact of life that you have to live with. >Certainly. But we should hope that everyone is striving to keep these >unproductive efforts to a minimum nowadays. > >: It's the reason for things like autoconf and MetaConfig. Perhaps using >: one of those two packages is the solution you're straining for. >If only these were easy to handle - I gave up an attempt to use autoconf >for my software after I realized that just getting the basics would >require me several hours of study - or is there any HOWTO or rather >mini-HOWTO available for autoconf? I have no idea. Since many many many packages are autoconf'ed I don't think that it can be that hard. I usually just use some preexisting package as a template. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com