在构建我的C ++可执行文件（gcc）时，我可以获得所有链接的库的报告吗？ （包括静态链接）

我有一个我继承的C ++应用程序，它包括：

I have a C++ application that I inherited, which consists of:

• 我的主要应用程序


• 几个应用程式特定的程式库（libapp1，libapp2等）


• 几个「第三方」程式库（大多数「第三方只是公司其他团队」）无论是主应用程序，从应用程序特定的libappX库，以及从其他第三方库 - 例如libext1，libext2，etc ...

换句话说，我的代码如下所示：

In other words, my code looks like this:

// main.C
#include <app1/a1l1.H>
#include <app2/a2l1.H>
#include <ext1/e1l1.H>

// app1/a1l1.H
#include <app1/a1l2.H>
#include <ext2/e2l1.H>

// app2/a2l1.H
#include <ext2/e2l2.H>

// ext1/e1l1.H
#include <ext3/e3l1.H>

// ext3/e3l1.H
#include <ext4/e4l1.H>

问题：

1）我如何知道哪些库已经链接到最终的可执行文件？ 这必须包括静态链接

1) How can I tell which libraries have been linked into the final executable? This must include statically linked ones

换句话说，我想要回答app1，app2，ext1，ext2，ext3，ext4

In other words, I want an answer of "app1, app2, ext1, ext2, ext3, ext4"

理想情况下，答案将从可执行文件本身（我有一个调试版本的内置的情况下，它使更可能）。如果这是不可能的，我想知道是否有一个简单的代码分析工具（在gcc本身内部的东西）提供分析。

Ideally, the answer would be available from the executable itself (I have a debug version of it built in case it makes it more possible). If that's impossible, i'd like to know if there's a simple code analysis tool (iedeally something within gcc itself) to provide that analysis.

请注意，目标文件对于外部库已经构建，所以查看构建日志以查看链接，我担心ext4将不会显示在日志中，因为我们不会建立ext3库已经预先内置。

Please note that the object files for external libraries are already built, so looking at the build logs to see what was linked, I'm worried that "ext4" won't show up in the log since we won't be building "ext3" library that is already pre-built.

注意：使用DEPS设置为yes来运行nmake，重建所有的不是一个选项。但我可以访问外部库的完整的源代码。

NOTE: running "nmake" with DEPS set to yes to rebuild all the is NOT an option. But i DO have access to the full source code for external libraries.

2）一个稍微分开和不太重要的问题，我怎么能告诉所有包含文件用于我正在构建的整个源代码树。再次，理想情况下，frm已经构建的可执行文件，我有一个调试版本。

2) A slightly separate and less important question, how can i tell a list of all the include files used in the entire source tree I'm building. Again, ideally frm already-built executable, which i have a debug version of.

=================

=================

更新：为了说明，我们的库是静态链接的，因此 ldd （List Synamic Dependencies）不工作。

UPDATE: Just to clarify, our libraries are linked statically, so ldd (List Synamic Dependencies) does not work.

此外，答案可以是Solaris或Linux - 无所谓。

Also, the answer can be either for Solaris or Linux - doesn't matter.

我尝试使用 nm 但是没有列出库

I tried using nm but that doesn't list the libraries