blocks|key|1425727|text|也许你在找这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1425728|ld+-r+src1.o+src2.o+src3.o+-o+final.o|code-block|syntax|javascript|1425729|但是让他们存档总是很好的，使用|1425730|ar+rvs+libmy.a+file1.o+file2.o+file3.o|offset|length|style|CODE|1425731|然后使用-lmy链接。|1425732|entityMap^0|0|0|0|0|12|0|4|4|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@$K|Z|L|10|M|N]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

May be you're looking for this :

<pre><code>ld -r src1.o src2.o src3.o -o final.o
</code></pre>

But its always nice to have them archived, using

<code>ar rvs libmy.a file1.o file2.o file3.o</code>

Then use <code>-lmy</code> to link.

blocks|key|288430|text|无法将多个源文件编译为单个对象文件。对象文件是单个源文件及其头部(也称为https://en.wikipedia.org/wiki/Translation_unit_(programming%2529)+)的编译结果。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|288431|如果要组合已编译的文件，通常使用ar命令将其组合到静态库中：|style|CODE|288432|$+ar+cr+libfoo.a+file1.o+file2.o+file3.o|code-block|syntax|javascript|288433|然后，您可以在链接时使用这个静态库，或者将其直接作为对象文件传递：|288434|$+gcc+file4.o+libfoo.a+-o+myprogram|288435|或将其链接为带有-l标志的库。|288436|$+gcc+file4.o+-L.+-lfoo+-o+myprogram|288437|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Translation_unit_(programming%2529)|1|http://linux.die.net/man/1/ar^0|10|1R|0|0|G|2|G|2|1|0|0|0|0|8|2|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@$A|19|B|1A|F|G]]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|H|3|I|5|J|7|1E|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1G|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1H|8|@$A|1I|B|1J|F|G]]|9|@]|C|$]]|$1|S|3|T|5|J|7|1K|8|@]|9|@]|C|$K|L]]|$1|U|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]|12|$5|X|Y|Z|C|$10|13]]]]

You can't compile multiple source files into a single object file. An object file is the compiled result of a single source file and its headers (also known as a <a href="https://en.wikipedia.org/wiki/Translation_unit_(programming)" rel="noreferrer">translation unit</a>).

If you want to combine compiled files, it's usually combined into a static library using the <a href="http://linux.die.net/man/1/ar" rel="noreferrer"><code>ar</code></a> command:

<pre><code>$ ar cr libfoo.a file1.o file2.o file3.o
</code></pre>

You can then use this static library when linking, either passing it directly as an object file:

<pre><code>$ gcc file4.o libfoo.a -o myprogram
</code></pre>

Or linking with it as a library with the <code>-l</code> flag

<pre><code>$ gcc file4.o -L. -lfoo -o myprogram
</code></pre>

blocks|key|288458|text|这并不是通常的做法，但您可以通过创建一个具有以下内容的新final.c文件轻松地实现您想要的结果。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|288459|#include+"src1.c"
#include+"src2.c"
#include+"src3.c"|code-block|syntax|javascript|288460|然后，您可以按以下方式编译它。|288461|gcc+-c+final.c+-o+final.o|288462|请注意，即使每个文件在单独编译时成功编译，也可能存在问题，请阅读编译错误。当以这种方式将源文件合并到单个源文件时，这种情况往往发生在宏定义和包含中。|288463|entityMap^0|S|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

This is not a usual way to proceed, but you can easily achieve what you want by creating a new <code>final.c</code> file with the following content.

<pre><code>#include "src1.c"
#include "src2.c"
#include "src3.c"
</code></pre>

Then you can compile it as follows.

<pre><code>gcc -c final.c -o final.o
</code></pre>

Note that there may be issues, read compilation errors, even if each file compiles successfully when compiled separately. This tend to happen especially with macro definitions and includes, when merging your source files into a single one this way.

blocks|key|4048252|text|要么创建一个包含所有.c文件的.c，然后使用gcc+-c+final.c命令编译这个最终文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4048253|或|4048254|另一种方法是使用archive.Build所有文件获取各自的.o，然后在一个库中存档，库中将包含所有这些.o文件。|4048255|entityMap^0|A|2|F|2|M|E|0|0|U|2|1G|2|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$]]

Either you make a <code>final.c</code> which will include all <code>.c</code> files then you can compile this final using <code>gcc -c final.c</code> command.

or

Another method is to use archive.Build all files to get respective <code>.o</code> then archive then in one library which will have all those <code>.o</code> file.

blocks|key|288490|text|试着使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|288491|gcc+-o+final+file1.c+file2.c+file3.c|code-block|syntax|javascript|288492|对我来说很管用。|288493|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

try using 

<pre><code>gcc -o final file1.c file2.c file3.c
</code></pre>

it works for me.

blocks|key|4048285|text|若要将多个源文件组合为单个对象文件(至少自gcc+4.1以来)，请使用编译器/链接器选项-组合|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4048286|(编辑)后来改为编译器选项-flto，并根据编译状态自动链接：Requirements+to+use+flto|offset|length|4048287|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/31688069/requirements-to-use-flto^0|0|V|O|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

To combine multiple source files into a single object file (at least since gcc 4.1), use the compiler/linker option --combine 

(edit) later replaced with the compiler option -flto, with linking automatic depending on the compilation state: <a href="https://stackoverflow.com/questions/31688069/requirements-to-use-flto">Requirements to use flto</a>

blocks|key|4048293|text|您可以始终将这些文件传送到GCC：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4048294|join+file1.c+file2.c+file3.c+%7C+gcc+-x+c+-c+-o+single.o+-|code-block|syntax|javascript|4048295|不要忘记指定语言"-x+c“的选项，它现在无法从文件扩展名中推导出来。你告诉GCC接受来自stdin的输入单尾短跑"-“。|4048296|请注意，这相当于编译包含以下内容的文件"final.c“：|4048297|#include+"file1.c"
#include+"file2.c"
#include+"file3.c"|4048298|使用|4048299|gcc+-c+-o+single.o+final.c|4048300|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

You can always pipe the files to GCC:

<pre><code>join file1.c file2.c file3.c | gcc -x c -c -o single.o -
</code></pre>

Don't forget the option specifying the language, "-x c", which now cannot be deduced from the file extension. You tell GCC to accept input from stdin with the single trailing dash "-".

Note that this is equivalent to compiling a file "final.c" with following contents:

<pre><code>#include "file1.c"
#include "file2.c"
#include "file3.c"
</code></pre>

With

<pre><code>gcc -c -o single.o final.c
</code></pre>

blocks|key|1425868|text|我只想说。这是一个缺失的特征。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1425869|为什么？|1425870|假设cc可以是clang或gcc|offset|length|style|CODE|1425871|cc+-c+t1.c+t2.c+(multi-files+at+once)|code-block|syntax|javascript|1425872|vs|1425873|cc+-c+t1.c+
cc+-c+t2.c
...
(one+by+one)|1425874|有什么关系？|1425875|输出.o是相同的，尽管一个方法可以指定-o+name，当您在自定义工具链中使用cc时，它可能很有用。|1425876|不同之处在于性能。除了启动cc的时间之外，如果多个文件使用相同的.h头文件集(在大多数情况下它们会使用)。头文件可以加载一次而不是每个文件。|1425877|如果使用多个库，则头文件可能很大。一个典型的.pch+(预编译头)文件可以大到10+as。|1425878|在我的小项目的真实生活测试中。我使用.cpp将所有的.cpp合并成一个.cpp，编译时间从600+ms缩短到300+ms。|1425879|c/cpp编译速度慢，因此这对于特性非常有用。|1425880|能喜欢|1425881|cc+-c+t1.c+-o+t1.o++t2.c+-o+t2.o+(specify+output+name+per+file)|1425882|或|1425883|cc+-c+t1.c++t2.c+-o+mylib.a+(If+some+one+say+.o+can't+be+combined
+++,+then+link+to+a+lib+in+one+command+line)|1425884|我希望clang或gcc能看到这一点。但是，即使他们能够同意这个观点，也不必费心等待修复。(开源开发人员争论说，除非他们从self那里意识到了一些东西，否则他们是非常绝望的。)您可以尝试其他答案中提到的方法，如|1425885|#include+"file1.c"
#include+"file2.c"
#include+"file3.c"|1425886|entityMap^0|0|0|2|2|7|5|D|3|0|0|0|0|0|J|7|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1K|8|@$F|1L|G|1M|H|I]|$F|1N|G|1O|H|I]|$F|1P|G|1Q|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|1R|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1T|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1U|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1V|8|@$F|1W|G|1X|H|I]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|20|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|21|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|22|8|@]|9|@]|A|$]]|$1|16|3|17|5|L|7|23|8|@]|9|@]|A|$M|N]]|$1|18|3|19|5|6|7|24|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|L|7|25|8|@]|9|@]|A|$M|N]]|$1|1C|3|1D|5|6|7|26|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|L|7|27|8|@]|9|@]|A|$M|N]]|$1|1G|3|-4|5|6|7|28|8|@]|9|@]|A|$]]]|1H|$]]

Just want to say. This is a missing feature.
Why?
say <code>cc</code> can be <code>clang</code> or <code>gcc</code>
<pre><code>cc -c t1.c t2.c (multi-files at once)
</code></pre>
vs
<pre><code>cc -c t1.c 
cc -c t2.c
...
(one by one)
</code></pre>
What is the difference?
The output .o is same, though the one by one way can specify <code>-o name</code> which may useful when you use cc in your customized toolchain.
The difference is performance. Besides the time for starting up cc, if multi files use same set of .h header files(In most case they will). The header files can load once instead of per file.
Header files could be huge if you use several libraries. A typical .pch (pre-compiled-header) file can as large as 10MB.
In real life test on my small project. I combined all .cpp into one .cpp using <code>#include &quot;others.cpp&quot;</code> , the compile time reduced from 600 ms to 300 ms.
The c/cpp compiles slow, so this could be so useful to be a feature.
could like
<pre><code>cc -c t1.c -o t1.o t2.c -o t2.o (specify output name per file)
</code></pre>
or
<pre><code>cc -c t1.c t2.c -o mylib.a (If some one say .o can't be combined
 , then link to a lib in one command line)
</code></pre>
I hope clang or gcc develop can see this. But not bothering to wait for a fix even they could agreed this opinion.(argue among open source developers can be very hopeless, unless they realize something from self). You can try the method mentioned in other answers like
<pre><code>#include &quot;file1.c&quot;
#include &quot;file2.c&quot;
#include &quot;file3.c&quot;
</code></pre>

I have some C source files and I am using <code>gcc</code>. I basically want to compile all of them and create one single object file. When I try:

<pre><code>gcc -c src1.c src2.c src3.c -o final.o
</code></pre>

I get:

<pre><code>gcc: cannot specify -o with -c or -S with multiple files
</code></pre>

If I try:

<pre><code>gcc -c src1.c src2.c src3.c
</code></pre>

I get three different object files. How can I tell <code>gcc</code> to compile all files to return one single object file (I also want to specify its name)? Thank you.

Maybe there is another more common approach to this, in this case please tell me.

Compile multiple C source fles into a unique object file

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一些C源文件，我正在使用gcc。基本上，我希望编译所有这些文件并创建一个单一的对象文件。当我尝试：gcc -c src1.c src2.c src3.c -o final.o我得到：gcc: cannot specify -o with -c or -S with multiple files如果我试着：gcc -...

问将多个C源代码编译成一个唯一的对象文件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将多个C源代码编译成一个唯一的对象文件EN