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
For each stable release, we publish pre-compiled **zip** archives for various platforms on the [releases page](https://github.com/icsm-au/dynadjust/releases/latest).
19
+
For each stable release, we publish pre-compiled **zip** archives for various platforms on the [releases page](https://github.com/geoscienceaustralia/dynadjust/releases/latest).
20
20
21
21
| Zip file (example) | Platform | BLAS/LAPACK backend | Link type |
|`dynadjust-linux-static.zip`| Any modern x86‑64 Linux | OpenBLAS | static |
29
29
30
-
Note that we build DynAdjust in two flavours: dynamic and static.
30
+
Note that we build DynAdjust in two flavours: *dynamic* and *static*.
31
31
32
32
The *dynamic* build keeps the executable small and relies on shared system libraries that are already present, distributed by the operating system, or shared across multiple software packages. That means security patches and performance upgrades (e.g., new Intel MKL version) arrive automatically through normal system updates.
33
33
34
-
The *static* build moves in the opposite direction: we compile every required library directly into one self-contained binary. Nothing else has to be installed for the program to run, which is invaluable when we need to run DynAdjust in the cloud or in production as it provides an exact version for regulatory reproducibility. Because it is insulated from future changes in operating-system libraries, it gives us a deterministic, "known-good" binary that will behave identically next year even if the underlying machines, operating systems, or libraries are patched or replaced.
34
+
The *static* build moves in the opposite direction: we combine every required library directly into one self-contained binary. Nothing else has to be installed for the program to run, which is invaluable when DynAdjust needs to be run in the cloud or in production as it provides an exact version for regulatory reproducibility. Because it is insulated from future changes in operating-system libraries, it gives us a deterministic, "known-good" binary that will behave identically even after the underlying machines, operating systems, or libraries are patched or replaced.
35
35
36
36
Maintaining both variants therefore gives us flexibility: the dynamic build inherits dependency updates automatically, while the static build guarantees portability and long-term reproducibility in controlled settings.
37
37
38
-
Each archive contains the six command‑line tools:
38
+
Each archive contains the seven command‑line tools:
For dynamic builds additional shared libraries (`.dll`, `.so`, `.dylib`) are included and each DynAdjust command is broken into a wrapper executable and a shared library.
42
+
For dynamic builds, additional shared libraries (`.dll`, `.so`, `.dylib`) are included and each DynAdjust command is broken into a wrapper executable and a shared library.
0 commit comments