[Top][All Lists]

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

Re: about what goes into a distribution file

From: Reuben Hawkins
Subject: Re: about what goes into a distribution file
Date: Wed, 23 Feb 2011 20:33:07 -0800

On Sat, Feb 19, 2011 at 11:49 PM, Ralf Wildenhues <address@hidden>wrote:

> Hi Vincent,
> * Vincent Torri wrote on Fri, Feb 18, 2011 at 08:33:01AM CET:
> > from the automake documentation, all the files read by AC_CONFIG_FILES
> are
> > added in the distribution. But why aren't the generated files not in the
> > tarball (the are in but not the .pc for example) ?
> Just to answer the question for whoever else stumbles over this:
> because the point of generating them is that they may look differently
> on different systems.  Thus it makes no sense to distribute them.
> And actually, the rules are a bit more complicated: the .in files are
> distributed only if they are mentioned literally in (i.e.,
> not as shell variable), and when they are not the output file of another
> AC_CONFIG_FILES command (e.g., -> -> foo).  The gory
> details are documented here:
> Cheers,
> Ralf

Hi Ralf,

The attached project (a trivial flex scanner) built with "make dist"
includes scanner.c (generated by flex from scanner.l).  Why is scanner.c
included?  Can I somehow prevent it from being include without setting up a
dist-hook rule?

Thanks in advance,

Attachment: test-scanner-1.tar.gz
Description: GNU Zip compressed data

reply via email to

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