2020.12.22 13:59 "[Tiff] Naming of the 'libtiff' libraries in Windows - proposal", by Miguel Medalha

2020.12.23 13:04 "Re: [Tiff] Naming of the 'libtiff' libraries in Windows - proposal", by Roger Leigh

I understand your reasoning and you are most probably right. As for the static version of the library, I still think it would be a worthwhile insertion. The building of other projects needs a static version of the tiff library, and as it is the dynamic library is overwritten by the static library when built with 'cmake -DBUILD_SHARED_LIBS:BOOL=OFF’. This insertion would enable the coexistence of both libraries inside the same directory.


Resulting in 'tiff-static.lib'.

What do you think?

I think this is a compatibility break as well, since you’ve changed the name of the static library in a backward-incompatible way.

The expectation with the CMake build is that you use BUILD_SHARED_LIBS to choose static or shared. There are no naming conflicts because there’s only one variant being built. The existing FindTIFF.cmake will find either the static or shared version using the existing naming conventions. Adding the -static suffix will break that.

I don’t understand the actual requirements here. If you are using the static version, why are you also building a dynamic version? On Windows, it’s simply not possible for the two to coexist. You can rename one of them as you have suggested, but it is absolutely going to break long standing assumptions in many projects, as well as the existing CMake support and doubtless support in other tools as well.