|
From: Jannick <thi...@gm...> - 2016-10-05 21:47:31
|
Hey Eli, On Oct 04, 2016 at 12:00 PM, Eli Zaretskii wrote: > > > From: "Jannick" <thi...@gm...> > > Date: Tue, 4 Oct 2016 11:15:43 +0200 > > > > BTW: Is there an easy standard *one-step* approach to determine the > > complete dependency graph of (non-Windows) libraries to be linked with > > given the 'root libraries' which are linked in the first place? In the > > example above/below that would mean that the libraries 'libiberty.a', > > 'libintl.a', 'libiconv.a' and 'libz.a' are spit out somehow given the > > root library 'libbfd.a'. > > Get the dependency walker: > > http://www.dependencywalker.com/ Indeed, this is very interesting. I will try to use the dependency walker to have an automated approach to determine all dependencies (other than system dll's) of an executable. Thanks, J. |