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
After adding the file, logout and login again. Opening a new terminal will not be sufficient.
69
+
After adding the file, log out and in again. Opening a new terminal will **not** be sufficient.
70
+
Verify the changes by listing the loaded environment in a new terminal:
70
71
71
-
## Using directly from the binary directory
72
+
```terminal
73
+
systemctl show-environment
74
+
```
72
75
73
-
{% warning %}
74
-
This method is strongly discouraged unless you are a preCICE developer.
75
-
Install preCICE into a prefix unless you have a very good reason not to.
76
-
{% endwarning %}
76
+
## Using directly from the binary directory
77
77
78
-
It may not always be practical to install preCICE repeatedly.
79
-
This is especially the case for simultaneous development of preCICE and an adapter, or while profiling the internals.
78
+
It may not always be practical to reinstall preCICE repeatedly.
79
+
This is especially the case for simultaneous development of preCICE and an adapter or while profiling the internals.
80
80
81
-
This method is discouraged as file layouts are fundamentally different and we make **no** guarantees on keeping them consistent between releases.
82
-
Hence, the only reliable methods for using preCICE from the binary directory require `pkg-config` or `CMake`.
83
-
If your adapter or solver isn't using one of these methods, then we strongly suggest to install preCICE to a prefix or port the adapter to `pkg-config`.
81
+
This method is discouraged as file layouts are fundamentally different, and we make **no** guarantees on keeping them consistent across releases.
82
+
Hence, the only reliable methods for using preCICE from the binary directory require pkg-config or CMake.
83
+
If your adapter or solver isn't using one of these methods, we strongly suggest installing preCICE to a prefix or porting the adapter to pkg-config or CMake.
84
84
85
-
First extend `LD_LIBRARY_PATH` with the binary directory if you don't plan to use `rpath` (which `CMake` does by default).
86
-
For `pkg-config` users, extend `PKG_CONFIG_PATH` with the binary directory.
87
-
For `CMake` users, either set the environment variable `precice_DIR` to the binary directory prior to calling `CMake`, or pass it as a `CMake` variable during configuration.
85
+
First, extend `LD_LIBRARY_PATH` with the binary directory if you don't plan to use `rpath` (which CMake does by default).
86
+
For pkg-config users, extend `PKG_CONFIG_PATH` with the binary directory.
87
+
For CMake users, either set the environment variable `precice_DIR` to the binary directory before calling CMake or pass it as a CMake variable during configuration.
88
88
89
89
```conf
90
90
# Only for using preCICE directly from the build directory
91
-
# (as of preCICE v3.3.0 - later versions might differ).
92
-
# Prefer installing to a prefix (see above).
91
+
# (as of preCICE v3.4.0 - later versions might differ).
If the binary `precice-version` cannot be found, then `PATH` is incorrect.
109
+
If the library `libprecice.so` cannot be found, then `LD_LIBRARY_PATH` is incorrect.
110
+
If the displayed version differs from the version you expect, then you have multiple conflicting preCICE installations on your system.
111
+
112
+
Next, run:
113
+
114
+
```terminal
115
+
pkg-config --modversion libprecice
116
+
```
117
+
118
+
If `libprecice` wasn't found, then your `PKG_CONFIG_PATH` is incorrect.
119
+
If the displayed version differs from the version you expect, then you have multiple conflicting preCICE installations on your system.
120
+
121
+
At this point, check whether the installation step was successful and whether the used installation prefix contains folders `bin`, `lib`, and `include`.
122
+
101
123
## Next steps
102
124
103
-
This concludes the preCICE installation for custom prefixes and you should have a working installation of preCICE on your system.
125
+
This concludes the preCICE installation for custom prefixes.
126
+
You should now have a working preCICE installation on your system.
104
127
105
128
To use preCICE in your project, see the page [Linking to preCICE](installation-linking).
0 commit comments