Ralf Wildenhues wrote:
> * Bollinger, John C wrote on Mon, Sep 14, 2009 at 05:33:40PM CEST:
> > It seems that normally, the generated configure script creates dummy
> > *.Po files in the right places, thus masking the absence of Make
> rules
> > for that purpose. In my case, however, I used Make
On Tue, Sep 15, 2009 at 1:33 AM, Bollinger, John C
wrote:
> That would also help in the case where one or more $(DEPDIR)s is accidentally
> or cluelessly deleted -- the developer would not have to re-run configure
> (not an
> obvious solution) to fix the project directory.
Do you have to re-run
Hi,
In the automake docs at
http://sources.redhat.com/automake/automake.html#Alternative
the link to Peter Miller's paper "Recursive..." is broken.
After a quick search I found the abstract here
http://miller.emu.id.au/pmiller/books/rmch/
with a link to the paper in pdf here
http://aegis.sourcef
* Bollinger, John C wrote on Mon, Sep 14, 2009 at 05:33:40PM CEST:
> It seems that normally, the generated configure script creates dummy
> *.Po files in the right places, thus masking the absence of Make rules
> for that purpose. In my case, however, I used Make variables in
> Makefile.am to abbr
Ralf Wildenhues wrote:
> > (*) "More or less" because with Automake 1.11 it yielded Makefiles
> containing many lines of the form
> > include src/$(DEPDIR)/foo.Po
> > These files did not (yet) exist, so make completely rejected the
> file.
> > Automake stopped emitting these when I removed
