blocks|key|1345736|text|是的，这是相当简单的。只需使用两个"add_library“命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1345737|add_library(MyLib+SHARED+source1.c+source2.c)
add_library(MyLibStatic+STATIC+source1.c+source2.c)|code-block|syntax|javascript|1345738|即使您有许多源文件，也可以将源文件列表放在一个Cmake变量中，这样做仍然很容易。|offset|length|style|CODE|1345739|在Windows上，你可能应该给每个库起一个不同的名字，因为共享和静态都有一个".lib“文件。但是在Linux和Mac上，你甚至可以给这两个库起相同的名字(例如libMyLib.a和libMyLib.so)：|1345740|set_target_properties(MyLibStatic+PROPERTIES+OUTPUT_NAME+MyLib)|1345741|但我不建议将该库的静态版本和动态版本命名为相同的名称。我更喜欢使用不同的名称，因为对于链接到库的工具，在编译行上选择静态链接与动态链接更容易。通常我会选择像libMyLib.so+(共享)和libMyLib_static.a+(静态)这样的名称。(这些将是linux上的名称。)|1345742|entityMap^0|0|0|N|5|0|29|A|2K|B|0|0|26|B|2N|H|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$I|10|J|11|K|L]|$I|12|J|13|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|15|8|@$I|16|J|17|K|L]|$I|18|J|19|K|L]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$]]

Yes, it's moderately easy. Just use two &quot;add_library&quot; commands:
<pre><code>add_library(MyLib SHARED source1.c source2.c)
add_library(MyLibStatic STATIC source1.c source2.c)
</code></pre>
Even if you have many source files, you can place the list of sources in a <code>Cmake</code> variable, so it's still easy to do.
On Windows you should probably give each library a different name, since there is a &quot;.lib&quot; file for both shared and static. But on Linux and Mac you can even give both libraries the same name (e.g. <code>libMyLib.a</code> and <code>libMyLib.so</code>):
<pre><code>set_target_properties(MyLibStatic PROPERTIES OUTPUT_NAME MyLib)
</code></pre>
But I don't recommend giving both the static and dynamic versions of the library the same name. I prefer to use different names because that makes it easier to choose static vs. dynamic linkage on the compile line for tools that link to the library. Usually I choose names like <code>libMyLib.so</code> (shared) and <code>libMyLib_static.a</code> (static). (Those would be the names on linux.)

blocks|key|1130467|text|通常不需要为您的目的复制ADD_LIBRARY调用。只需利用|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1130468|$>+man+cmake+%7C+grep+-A6+'%5E+*BUILD_SHARED_LIBS$'+
+++BUILD_SHARED_LIBS
++++++++++Global+flag+to+cause+add_library+to+create+shared+libraries+if+on.

++++++++++If+present+and+true,+this+will+cause+all+libraries+to+be+built+shared+unless+the+library+was
++++++++++explicitly+added+as+a+static+library.++This+variable+is+often+added+to+projects+as+an+OPTION
++++++++++so++that+each+user+of+a+project+can+decide+if+they+want+to+build+the+project+using+shared+or
++++++++++static+libraries.|code-block|syntax|javascript|1130469|在构建时，首先(在一个源代码外目录中)使用-DBUILD_SHARED_LIBS:BOOL=ON，然后使用OFF。|1130470|entityMap^0|C|B|0|0|L|R|1H|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

There is generally no need to duplicate <code>ADD_LIBRARY</code> calls for your purpose. Just make use of

<pre><code>$&gt; man cmake | grep -A6 '^ *BUILD_SHARED_LIBS$' 
 BUILD_SHARED_LIBS
 Global flag to cause add_library to create shared libraries if on.

 If present and true, this will cause all libraries to be built shared unless the library was
 explicitly added as a static library. This variable is often added to projects as an OPTION
 so that each user of a project can decide if they want to build the project using shared or
 static libraries.
</code></pre>

while building, first (in one out-of-source directory) with <code>-DBUILD_SHARED_LIBS:BOOL=ON</code>, and with <code>OFF</code> in the other.

blocks|key|1345878|text|这确实是有可能的。正如@Christopher+Bruns在他的回答中所说，你需要添加两个版本的库：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1345879|set(libsrc+source1.c+source2.c+source3.c)
add_library(mylib-static+STATIC+${libsrc})
add_library(mylib-shared+SHARED+${libsrc})|code-block|syntax|javascript|1345880|然后，如here所述，您需要指定两个目标应该使用相同的输出名称，并且不覆盖彼此的文件：|offset|length|1345881|SET_TARGET_PROPERTIES(mylib-static+PROPERTIES+OUTPUT_NAME+mylib+CLEAN_DIRECT_OUTPUT+1)
SET_TARGET_PROPERTIES(mylib-shared+PROPERTIES+OUTPUT_NAME+mylib+CLEAN_DIRECT_OUTPUT+1)|1345882|这样，您将同时获得libmylib.a和libmylib.so+(在Linux上)或mylib.lib和mylib.dll+(在Windows上)。|1345883|entityMap|0|LINK|mutability|MUTABLE|url|https://cmake.org/pipermail/cmake/2007-January/012669.html^0|0|0|4|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@$I|Z|J|10|1|11]]|A|$]]|$1|K|3|L|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

It is indeed possible. As @Christopher Bruns said in his answer, you need to add two versions of the library:

<pre><code>set(libsrc source1.c source2.c source3.c)
add_library(mylib-static STATIC ${libsrc})
add_library(mylib-shared SHARED ${libsrc})
</code></pre>

Then, as described <a href="https://cmake.org/pipermail/cmake/2007-January/012669.html" rel="nofollow noreferrer">here</a>, you need to specify that both targets should use the same output name and not overwrite each other's files:

<pre><code>SET_TARGET_PROPERTIES(mylib-static PROPERTIES OUTPUT_NAME mylib CLEAN_DIRECT_OUTPUT 1)
SET_TARGET_PROPERTIES(mylib-shared PROPERTIES OUTPUT_NAME mylib CLEAN_DIRECT_OUTPUT 1)
</code></pre>

This way, you will get both libmylib.a and libmylib.so (on Linux) or mylib.lib and mylib.dll (on Windows).

blocks|key|1130638|text|正如前面的答案中所建议的那样，可以将所有东西都打包在相同的编译气息中，但我建议不要这样做，因为最终这是一种只适用于简单项目的技巧。例如，在某些情况下，您可能需要针对不同版本的库使用不同的标志。在Windows上，标志通常用于在导出或不导出符号之间切换)。或者如上所述，您可能希望将.lib文件放到不同的目录中，这取决于它们是对应于静态库还是共享库。这些障碍中的每一个都需要一个新的技巧。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1130639|这可能是显而易见的，但是一个以前没有提到的替代方案是将库的类型作为参数：|1130640|set(+${PROJECT_NAME}_LIBTYPE+CACHE+STRING+"library+type"+)
set_property(+CACHE+${PROJECT_NAME}_LIBTYPE+PROPERTY+STRINGS+"SHARED;STATIC"+)
add_library(+${PROJECT_NAME}+${PROJECT_NAME}_LIBTYPE+${SOURCE_FILES}+)|code-block|syntax|javascript|1130641|将库的共享和静态版本放在两个不同的二叉树中，可以更容易地处理不同的编译选项。我看不出保持编译树的不同有什么严重的缺点，特别是如果你的编译是自动化的。|1130642|请注意，即使您打算使用中间OBJECT库(具有上面提到的警告，因此您需要一个令人信服的理由这样做)来实现编译的互互化，您仍然可以将端库放在两个不同的项目中。|1130643|entityMap^0|3W|4|0|0|0|0|D|6|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|R|$]]

It's possible to pack eveything in the same compilation breath, as suggested in the previous answers, but I would advise against it, because in the end it's a hack that works only for simple projects. For example, you may need at some point different flags for different versions of the library (esp. on Windows where flags are typically used to switch between exporting symbols or not). Or as mentionned above, you may want to put <code>.lib</code> files into different directories depending on whether they correspond to static or shared libraries. Each of those hurdles will require a new hack.
It may be obvious, but one alternative that has not been mentionned previously is to make the type of the library a parameter:
<pre><code>set( ${PROJECT_NAME}_LIBTYPE CACHE STRING &quot;library type&quot; )
set_property( CACHE ${PROJECT_NAME}_LIBTYPE PROPERTY STRINGS &quot;SHARED;STATIC&quot; )
add_library( ${PROJECT_NAME} ${PROJECT_NAME}_LIBTYPE ${SOURCE_FILES} )
</code></pre>
Having shared and static versions of the library in two different binary trees makes it easier to handle different compilation options. I don't see any serious drawback in keeping compilation trees distinct, especially if your compilations are automated.
Note that even if you intend to mutualize compilations using an intermediate <code>OBJECT</code> library (with the caveats mentionned above, so you need a compelling reason to do so), you could still have end libraries put in two different projects.

blocks|key|1346080|text|请注意，前面的答案不适用于MSVC|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1346081|add_library(test+SHARED+${SOURCES})
add_library(testStatic+STATIC+${SOURCES})
set_target_properties(testStatic+PROPERTIES+OUTPUT_NAME+test)|code-block|syntax|javascript|1346082|CMake将与test.lib和test.exp一起为shared目标创建test.dll。然后，它将在同一目录中为static目标创建test.lib，并替换以前的目录。如果您尝试将一些可执行文件链接到shared目标，它将失败，并显示如下错误：|1346083|error+LNK2001:+unresolved+external+symbol+__impl_*.`.|1346084|请使用ARCHIVE_OUTPUT_DIRECTORY，并为static目标使用一些唯一的输出目录：|1346085|add_library(test+SHARED+${SOURCES})
add_library(testStatic+STATIC+${SOURCES})
set_target_properties(
++testStatic+PROPERTIES
++OUTPUT_NAME+test
++ARCHIVE_OUTPUT_DIRECTORY+testStatic
)|1346086|test.lib将在testStatic目录中创建，并且不会覆盖test目标中的test.lib。它与MSVC配合使用非常完美。|1346087|entityMap^0|D|4|0|0|7|8|G|8|R|6|11|8|1M|6|1W|8|2U|6|0|0|3|O|U|6|0|0|0|8|A|A|W|4|14|8|1F|4|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1F|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1L|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1X|8|@]|D|@]|E|$]]]|V|$]]

Please be aware that previous answers won't work with <code>MSVC</code>:
<pre><code>add_library(test SHARED ${SOURCES})
add_library(testStatic STATIC ${SOURCES})
set_target_properties(testStatic PROPERTIES OUTPUT_NAME test)
</code></pre>
CMake will create <code>test.dll</code> together with <code>test.lib</code> and <code>test.exp</code> for <code>shared</code> target. Than it will create <code>test.lib</code> in the same directory for <code>static</code> target and replace previous one. If you will try to link some executable with <code>shared</code> target it will fail with error like:
<pre><code>error LNK2001: unresolved external symbol __impl_*.`.
</code></pre>
Please use <code>ARCHIVE_OUTPUT_DIRECTORY</code> and use some unique output directory for <code>static</code> target:
<pre><code>add_library(test SHARED ${SOURCES})
add_library(testStatic STATIC ${SOURCES})
set_target_properties(
 testStatic PROPERTIES
 OUTPUT_NAME test
 ARCHIVE_OUTPUT_DIRECTORY testStatic
)
</code></pre>
<code>test.lib</code> will be created in <code>testStatic</code> directory and won't override <code>test.lib</code> from <code>test</code> target. It works perfect with <code>MSVC</code>.

Same source, all that, just want a static and shared version both. Easy to do?

Is it possible to get CMake to build both a static and shared library at the same time?

Windows

Linux

同样的源代码，所有这些，只是想要一个静态和共享的版本。一苇可航?

问有没有可能让CMake同时构建静态库和共享库？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有可能让CMake同时构建静态库和共享库？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有可能让CMake同时构建静态库和共享库？
EN