The forthcoming Automake release is about to break the means I have
been using to automatically version my package (without manually
editing configure.ac) for the past 9 years. I am told to use m4 code
in the AC_INIT arguments in order to supply package versioning
information. This is what I
On Tue, May 22, 2012 at 12:06 PM, Nick Bowler wrote:
> Probably all you need to do is add these generated files to CLEANFILES,
> e.g.,
>
> CLEANFILES = git_version.py git_version.sed
>
> so that "make clean" deletes them.
Actually thinking about this in more detail, git_version.py should not
be
On Tue, May 22, 2012 at 2:30 PM, Nick Bowler wrote:
> Since you listed the LALAppsVCSInfo.h file in lalapps_version_SOURCES
> variable, that header got included in your distribution tarball. It
> therefore was not generated at all during the build done by distcheck,
> so nothing needed to be cle
On 2012-05-22 13:05 -0500, Adam Mercer wrote:
> On Tue, May 22, 2012 at 12:06 PM, Nick Bowler
> wrote:
>
> > Probably all you need to do is add these generated files to CLEANFILES,
> > e.g.,
> >
> > CLEANFILES = git_version.py git_version.sed
> >
> > so that "make clean" deletes them.
>
> I'd
On Tue, May 22, 2012 at 12:06 PM, Nick Bowler wrote:
> Probably all you need to do is add these generated files to CLEANFILES,
> e.g.,
>
> CLEANFILES = git_version.py git_version.sed
>
> so that "make clean" deletes them.
I'd thought of that, but what puzzles me (and the reason I didn't use
it)
Hello Adam,
On 2012-05-22 11:10 -0500, Adam Mercer wrote:
> Hi
>
> For one of my projects I'm running into an error where distcheck fails
> with the error:
>
> ERROR: files left in build directory after distclean:
> ./lalapps/src/lalapps/git_version.py
> ./lalapps/src/lalapps/git_version.sed
>
Hi
For one of my projects I'm running into an error where distcheck fails
with the error:
ERROR: files left in build directory after distclean:
./lalapps/src/lalapps/git_version.py
./lalapps/src/lalapps/git_version.sed
Why are these files remaining and how should I ensure they are removed
correc
>> (1) If the user unpacks the tarball, the rules are not executed.
>> (2) If the user does a bootstrap from the repository to do `make
>> dist', they are needed.
>> (3) If the user changes a doc source file in the tarball and wants
>> to regenerate the documentation, the rules are needed t
Werner LEMBERG writes:
> (1) If the user unpacks the tarball, the rules are not executed.
> (2) If the user does a bootstrap from the repository to do `make
> dist', they are needed.
> (3) If the user changes a doc source file in the tarball and wants to
> regenerate the documentation, the