[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: Re: [Automake] Making a Distribution

From: Tom Browder
Subject: Re: Re: Re: [Automake] Making a Distribution
Date: Thu, 21 Sep 2000 08:51:21 -0500

Since the distribution shouldn't be dependent upon autoconf and automake, why,
then are the *.am files shipped?

In any event, my has

  AC_OUTPUT(Makefile dir1/Makefile dir2/Makfile)

just as the example in the manual.

And the resulting's have reference to am scattered all through them!



-----Original Message-----
From: Ossama Othman <address@hidden>
To: address@hidden <address@hidden>
Date: Wednesday, September 20, 2000 12:21 PM
Subject: Re: Re: [Automake] Making a Distribution

>Hi Time,
>On Wed, Sep 20, 2000 at 11:04:21AM -0500, Tom Browder wrote:
>> Pavel, thanks for timely response.
>> I'm brand new to using automake/autoconf, and I'm using it to package a 
>> commercial
>> distribution of my company's product for a client.  I need the package to 
>> work on
>> both a Linux/GNU as well as an SGI/IRIX system.  When I test the 
>> distribution on the SGI,
>> the ./configure tries to use the *.am files and I get all kinds of 
>> dependency problems, and
>> I don't think my client will have automake or autoconf.  Shouldn't configure 
>> NOT require
>> (nor even try to use) autoconf or automake?  If not, why are the files 
>> automatically packaged
>> with the distribution?
>Your client does not need to have autoconf or automake installed since
>autoconf- and automake-aware packages are supposed to be
>self-contained.  Once you do a "make dist" ("dist" target is supplied
>by automake), your package should be completely decoupled from any
>external packaging tools such as autoconf and automake.  All your
>client needs to have is a Bourne shell compatible shell, and the make
>utility, in addition to whatever is needed to build your package.
>What does your AC_OUTPUT look like?  Your configure script should not
>be attempting to use the `.am' files at all.  It should be using the
>`' files generated by automake as input.  From those `.in'
>files, the configure script will generate Makefiles, etc.  Those `.in'
>files automatically get packaged with your distribution when you
>invoke "make dist."
>Ossama Othman <address@hidden>
>Distributed Object Computing Laboratory, Univ. of California at Irvine
>1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068  70E6 5EB7 5E71 F7A3 94A8
>Automake mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]