For new bug reports and feature requests, please open an issue in Github.
[TOC](#TOC)
<nameid="4"></a>
## 4 Platform Notes
@ -278,8 +274,8 @@ $ mkdir build ; cd build ;
$ cmake .. -G "Unix Makefiles"
$ make
```
[TOC](#TOC)
[TOC](#TOC)
<nameid="4-2"></a>
### 4.2 MacOS-X
@ -290,7 +286,6 @@ You should build and install libexpat and zlib from source.
You should build and install CMake from source.
[TOC](#TOC)
<nameid="4-3"></a>
### 4.3 MinGW/msys2
@ -347,7 +342,6 @@ $ make
The exiv2 command line program provides a `--grep` option which filters output. The implementation requires the header file `<regex.h>` and supporting library to be available during the build. When not available, the option degenerates to a substring match. Because there are multiple versions of `<regex.h>` available on the MinGW platform, detection of Regex is always disabled on this platform.
[TOC](#TOC)
<nameid="4-4"></a>
### 4.4 Cygwin
@ -363,7 +357,6 @@ Download and build cmake from source because I can't get the cygwin installed cm
To build cmake from source (for 3.11+), you need libncurses.
[TOC](#TOC)
<nameid="4-5"></a>
### 4.5 Microsoft Visual C++
@ -375,7 +368,6 @@ As well as Microsoft Visual Studio, you will need to install CMake, Python3, and
3) Conan can be installed using python/pip. Details in README-CONAN.md
[TOC](#TOC)
<nameid="5"></a>
## 5 Running the test suite
@ -386,41 +378,43 @@ The test suite is a mix of bash and python scripts. The python scripts are new
You can run the suite directly from the build:
```
$ make build
...
$ make tests
... lots of output ...
Summary report
```
You can run individual tests in the test directory using the environment string EXIV2_BINDIR to specify the location of the build artifacts:
You can run individual tests in the test directory using EXIV2\_BINDIR to specify the location of the build artifacts. For Cygwin and MinGW/msys builds, set EXIV2_EXT=.exe
```
rmills@rmillsmbp-w7 ~/gnu/github/exiv2/exiv2/build $ cd ../test
rmills@rmillsmbp-w7 ~/gnu/github/exiv2/exiv2/test $ env EXIV2_BINDIR=${PWD}/../build/bin make newtests
```
[TOC](#TOC)
<nameid="5-2"></a>
### 5.2 Running tests on Visual Studio builds
Use the bash interpreter for MinGW/msys2 to run the test suite.
Use the bash interpreter for MinGW/msys2 to run the test suite. It's essential to have a DOS Python3 interpreter on your path. The variables EXIV2\_BINDIR and EXIV2\_EXT enable the test suite to locate the MSVC build artifacts.
$ cd ...../build/../test
```
$ cd <exiv2dir>/build
$ cd ../test
$ PATH="/c/Python36:$PATH"
$ export EXIV2_EXT=.exe
$ export EXIV2_BINDIR=${PWD}/../build/bin
```
It's essential to have a DOS Python3 interpreter on your path.
$ PATH="/c/Python36:$PATH"
These variables enables the test suite to locate the MSVC build artifacts and you can follow the guidelines for UNIX-like systems above.
You can proceed to execute the components of the test suite as described for Unix type systems: