|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Release 3.4.3" |
| 4 | +date: 2024-03-21 |
| 5 | +categories: news |
| 6 | +author: "Cris Luengo" |
| 7 | +--- |
| 8 | + |
| 9 | +*DIPlib* 3.4.3 was released today. It fixes some deployment issues and a bug. |
| 10 | +Please see the [change log](/changelogs/diplib_3.4.3.html) for details. |
| 11 | + |
| 12 | +We recommend that all users upgrade to the new release. |
| 13 | + |
| 14 | +--- |
| 15 | + |
| 16 | +## For use from Python |
| 17 | + |
| 18 | +Install through [PyPI](https://pypi.org/project/diplib/) using |
| 19 | + |
| 20 | + pip install diplib |
| 21 | + |
| 22 | +We support Python 3.8 through 3.12, on Windows (x86_64), Linux (x86_64) and macOS (x86_64 and aarch64). |
| 23 | + |
| 24 | +All of these are 64-bit versions only. If you use a different platform, or a different version |
| 25 | +of Python, you will need to build from source. This is not complicated. We have |
| 26 | +[simple and clear instructions available](/diplib-docs/building_diplib.html). |
| 27 | + |
| 28 | +## For use from MATLAB |
| 29 | + |
| 30 | +We haven't created any pre-built installers for this version of DIPlib. |
| 31 | +You will need to build from source. This is not complicated. We have |
| 32 | +[simple and clear instructions available](/diplib-docs/building_diplib.html). |
| 33 | + |
| 34 | +## For use from C++ |
| 35 | + |
| 36 | +Please build from source. This should be a lot easier for you than messing |
| 37 | +with pre-compiled libraries and their linker compatibility issues. We recommend that you use *CMake* |
| 38 | +to build a project using *DIPlib*, either using the *DIPlib* repository as a sub-project, or following |
| 39 | +[this example *CMake* file](https://github.com/DIPlib/diplib/blob/master/examples/independent_project/CMakeLists.txt). |
| 40 | +If you don't want to use *CMake* for your project, then see |
| 41 | +[here](/diplib-docs/building_diplib.html#linking_diplib) for |
| 42 | +instructions on which preprocessor macros to define. |
| 43 | + |
| 44 | +Though there should be no need to change any of your code to use the new version of library, |
| 45 | +you might have to re-compile it, since some header files have changed. |
0 commit comments