Hi Bruno,
> * Bruno Haible wrote on Sun, May 31, 2009 at 12:50:13PM CEST:
> > - with a lazily computed version number (this is for projects where the
> > version
> > changes several times a day):
> >
> > AM_INIT_VERSION([$$version], [version=`sh $(top_srcdir)/gen-version`])
Here's a sligh
Hi Ralf,
Ralf Wildenhues wrote:
You could then experiment with suitable rules to keep the file up to
date, depending on the VCS. VCS hooks could ensure to update (or
remove, or otherwise outdate) the file. All rules that need the version
can just depend upon the file, and read from it afterwar
Hi everyone,
So I got all my code up and running and now I want to make a file so I can
use my library in another computer. Now, when I try to make dist-zip, I get:
aara...@~/Documents/workspace/cpputils$make dist-all
{ test ! -d "-cpputils--0.001" || { find "-cpputils--0.001" -type d ! -perm
-2
On Thu, 4 Jun 2009, Ralf Wildenhues wrote:
You could then experiment with suitable rules to keep the file up to
date, depending on the VCS. VCS hooks could ensure to update (or
remove, or otherwise outdate) the file. All rules that need the version
can just depend upon the file, and read from
Thanks again for the help Ralf.
>
> If that still doesn't help, it is useful to post a small example
>
> package.
>
Attached is an example package. What I left out of my original email was
that I'm putting the Makefile.am's out of the src/ directory to enable
building other architecture specific
* aaragon wrote on Thu, Jun 04, 2009 at 10:11:22PM CEST:
>
> So I got all my code up and running and now I want to make a file so I can
> use my library in another computer. Now, when I try to make dist-zip, I get:
>
> aara...@~/Documents/workspace/cpputils$make dist-all
> { test ! -d "-cpputils-
