[Top][All Lists]

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

Re: question about the *.Po files

From: Ralf Wildenhues
Subject: Re: question about the *.Po files
Date: Wed, 6 Apr 2005 13:34:10 +0200
User-agent: Mutt/1.4.1i

Hi Harald,

* Harald Dunkel wrote on Wed, Apr 06, 2005 at 01:22:14PM CEST:
> Ralf Wildenhues wrote:
> > 
> > Mostly compiler variations.  Automake's `depcomp' script knows different
> > ways to invoke compilers, so they output dependency information.  The
> > script itself does some reformatting, but not what you are hinting at.
> > So, the changes you observe might be due to differenc compilers or
> > compiler versions.
> I should have mentioned that both cases were generated by the
> same compiler. Of course in the first case the sources had to
> be saerched via vpath, so I had assumed that GNU make has
> created this absolute path name.

Really?  Oh.  Well.  Now that you mention it, it makes some sense.

> > Not that I know of.  You could try to amend `depcomp' to do this
> > reformatting, but it would probably be slow.  Furthermore, note that
> > quite a bit of the autotools silently assumes that you do not move the
> > build tree nor the source tree around, so you might encounter more
> > problems like this.
> Currently I have added a filter to my build script to replace
> the top level source directory path in the *.Po files by
> $(top_srcdir).
> There are several sed statements in depcomp, so I would assume
> that another sed would not hurt that much.

Yeah, I guess "slow" was an exaggeration.  Maybe you could hack it
into depcomp proper and suggest to include it (on the automake list)?
As optional behavior it might make sense for more than just you.


reply via email to

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