Re: question about the *.Po files

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

 



Ralf Wildenhues wrote:
> Hi Harald,
> 
> * Harald Dunkel wrote on Wed, Apr 06, 2005 at 10:01:56AM CEST:
> 
>>
>>How comes?
> 
> 
> 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.

> 
>>I like the second version, cause it allows me to rename my
>>sandbox directory without having to rebuild everything. Is
>>there a way to enforce this format?
> 
> 
> 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.


Regards

Harri

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux