You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: doc/setup/installing_prerequisites.adoc
+6-8
Original file line number
Diff line number
Diff line change
@@ -15,12 +15,12 @@ For other use cases like first trials to get started with OSI, dynamic linking c
15
15
16
16
== Windows
17
17
18
-
**Dynamic Linking (NOT RECOMMENDED)**
18
+
Dynamic Linking (NOT RECOMMENDED)::
19
19
20
20
Since on Windows symbols are not exported per default, it can be kind of annoying to deal with this during _protobuf_ header generation (see for example https://groups.google.com/g/protobuf/c/PDR1bqRazts).
21
21
That is an important reason to use static linking.
22
22
23
-
**Static Linking**
23
+
Static Linking::
24
24
25
25
Static linking might require to manually build _protobuf_.
26
26
It is important to notice that on Windows you can also specify how to link against the C runtime.
@@ -29,15 +29,13 @@ Basically, this can be set in CMake, e.g. https://cmake.org/cmake/help/latest/pr
29
29
Therefore, it could make sense to still dynamically link against the C Runtime when statically linking _protobuf_ / OSI.
30
30
(This is important e.g. when building shared libraries, since a static C runtime will create an isolated heap for your dll, which can lead to segfaults depending on what you expose on your public interfaces.)
31
31
32
-
The easiest way to achieve static linking on Windows without setting all the stuff manually in Cmake and building _protobuf_ is to actually use vcpkg:
33
-
34
-
**Install static _protobuf_ with dynamic c-runtime with vcpkg:**
32
+
The easiest way to achieve static linking on Windows without setting all the stuff manually in Cmake and building _protobuf_ is to actually **install static _protobuf_ with dynamic c-runtime with vcpkg**:
0 commit comments