[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 12:25:00 +0200
User-agent: Mutt/1.4.1i

Hi Harald,

* Harald Dunkel wrote on Wed, Apr 06, 2005 at 10:01:56AM CEST:
> I noted that sometimes the *.Po file for a *.o file looks
> like this
> utils/src/libbigint_a-bigint.o : \
>  \
>  /local/tmp/nbuild/sandboxsLSPpw/src/utils/src/ \
>  /usr/include/string.h /usr/include/features.h \

> and sometimes like this
> sound.o sound.o: ../../../src/mylib/sound.cxx ../../../include/common.h \
>   ../../include/config.h /usr/include/stdio.h /usr/include/features.h \
>   /usr/include/sys/cdefs.h /usr/include/gnu/stubs.h \
>   :
> Note the different path to the source files.
> 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 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.


reply via email to

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