On 2/4/24 8:00 PM, William Bader wrote:
Is it more complicated than trying to build the utilities with just the public header files to see what breaks, and then moving some declarations or wrappers to access them to a public header?
I gave that a go a few months ago, and it didn't end well. It's certainly possible that I didn't do it right, but I found myself copying functions out of the C/C++ code, etc. before I concluded that I wasn't going that route.
I could probably handle an occasional request with a cve and example tiff that is reproducible on Linux x86_64.
These are the ones that I'm told need to be fixed: https://gitlab.com/libtiff/libtiff/-/issues/?sort=created_date&state=closed&label_name%5B%5D=wontfix-unmaintained Thanks, Lee.
_______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
