Closed tuffnatty closed 9 months ago
This allows non-strict bcc build to finish when using the free non-C99-compliant Borland C++ 5.5 compiler.
C89/90 maintenance burden plus a slight number of CVE security issues... https://www.cvedetails.com/vulnerability-list/vendor_id-2224/Libtiff.html libtiff seems to be used by Harbour core developers, it even received patches for WinCE in the past is it still the case?
I've added libtiff for convenience in 2012, but Harbour core or contribs never ended up depending on it for anything. Probably very few if anybody is using this. If someone does, it remains (of course) possible to build this outside Harbour. As part of core, it's a maintenance burden, with frequent CVEs, pending bugs, and a local patch to maintain, while making builds longer and more fragile for everybody. I deleted it in 2016.
OK, I am going to merge this.
Even @vszakats who added this has removed libtiff in his fork.