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
Especially for building on Windows, the use of **vcpkg** to handle dependencies is recommended.
30
+
31
+
Prerequisites::
32
+
* The environment variable `VCPKG_ROOT` must be set to the root of your vcpkg installation.
33
+
* For Windows static linking, the static-md triplet is recommended (see also <<static_dynamic_linking, Static/Dynamic Linking>> explained below)
34
+
35
+
Steps::
36
+
. Configure the build using the vcpkg preset:
37
+
+
38
+
----
39
+
cmake --preset default
40
+
----
41
+
. Perform the build:
42
+
+
43
+
----
44
+
cmake --build build
45
+
----
46
+
47
+
48
+
== Building without vcpkg
49
+
50
+
To build without vcpkg, you must ensure necessary prerequisites are installed and detectable by CMake. It is then usually enough to include the `osi-cpp` repository in your main `CMakeLists.txt`:
Static linking is the recommended way to package OSI FMUs for sharing with others to be integrated in a co-simulation: They should have minimal external dependencies in order to ensure maximum portability.
14
-
For other use cases like first trials to get started with OSI, dynamic linking could be an option as well.
60
+
Static linking is the recommended way to package OSI FMUs for sharing with others to be integrated in a co-simulation: They should have minimal external dependencies in order to ensure maximum portability. For other use cases dynamic linking could be an option and is thus explained below.
15
61
16
-
== Windows
62
+
=== Windows
17
63
18
64
Dynamic Linking (NOT RECOMMENDED)::
19
65
@@ -46,7 +92,7 @@ Now the protobuf libraries can be built automatically using:
0 commit comments