|
From: Tom H. <to...@co...> - 2005-11-11 10:43:58
|
In message <200...@cn...>
Yao Qi <qiy...@cn...> wrote:
> When I update files in VEX/ direcotry and rebuild Valgrind by 'make', it
> seems that libvex.a could not be rebuilt automatically except run 'make
> libvex.a' in VEX directory.
We know. We just haven't work out how to fix it without introducing
other problems.
> Now, all the TOOLs are dependent on VEX/libvex.a and coregrind/valgrind
> is not, so when run 'make' in top directory of source code tree, the
> updated files in VEX could not be compiled ,VEX/libvex.a could not be
> updated, and finally all the TOOLs will not re-link VEX/libvex.a. So
> everytime when I modify files in VEX directory, I should 'make libvex.a'
> in VEX to build libvex.a and 'make' in lackey/, for example, to link
> this new VEX/libvex.a to lackey or someother TOOLs.
The reason coregrind/valgrind is not dependent on it is because it
doesn't link with it, hence it is not dependent on it!
The only things dependent on libvex.a are the tool binaries so each
of those should have a dependency on it. I might even see if that works...
> The depedency of coregrind/valgrind on libvex.a may be added to remove this
> problem. I am not so sure of compilation dependency, and anyone here
> could confirm or deny this, thanks in advance!
That would be a bogus dependency.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|