third_party/exiv2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation update to withdraw support for MinGW. The code-base has not been modified and will probably build with MinGW. However Team Exiv2 will not support this platform.

Browse Source
This commit is contained in:
clanmills
2017-06-06 17:43:05 +01:00
parent ef64de084c
commit 10069bd05b
2 changed files with 5 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README-CMAKE
+3 -6
View File
@@ -22,18 +22,15 @@ STATUS:
The daily build on MinGW/32 is performed using autotools for Qt/Windows Users.
* The existing automake (./configure) will continue to be supported by exiv2
for at least v0.27 (and probably longer)
The msvc2003 project/solutions files are deprecated and will not be supported after v0.26.
The msvc project/solutions files will continue to be supported by exiv2
for at least v0.27 (and probably longer)
There is no plan to adopt CMake as the only build platform.
* Team Exiv2 no longer provide support for MinGW (with/without CMake)
Exiv2 is very difficult to build on MinGW with CMake.
This is discussed in TODO-CMAKE
Robin Mills
robin@clanmills.com
2016-10-25
2017-06-06
-------------------------------------------------------------------------------
TODO-CMAKE
+2 -5
View File
@@ -20,10 +20,7 @@ ToDo: * CMake/MinGW builds executables that do not work properly for v0.26
This is because MinGW links the wrong DLLs.
Team Exiv2 will not provide support for CMake/MinGW
The known issues with CMake/MinGW will be reported to Kitware.
We hope CMake/MinGW will be in a working state for Exiv2 v0.27
Team Exiv2 will no longer provide support for MinGW
Here are notes concerning CMake/MinGW
@@ -166,5 +163,5 @@ Here are notes concerning CMake/MinGW
Robin Mills
robin@clanmills.com
2016-10-03
2017-06-06