[Geotiff] cmake based build: why shared _and_ static?

Mario Emmenlauer mario at emmenlauer.de
Sat Dec 9 08:51:11 EST 2017


Dear geotiff developers,

thanks for the very nice software. A small question: why is the default
for cmake to build the shared and static version of the library? I would
prefer if only one would be built. I can use cmake's BUILD_SHARED_LIBS
option to pick. This is mostly the default for other software.

For me, this would also help to address the problem that MSVC Windows
names the import library identical to the static library by default.
libgeotiff solves this by changing the import library name, but this
opens a can of worms for me downstream.

Its not a huge problem because I can fix the issue myself and maintain
a small patch. But maybe it would be more "standard" if libgeotiff
just used cmake's BUILD_SHARED_LIBS?

All the best,

    Mario Emmenlauer


--
BioDataAnalysis GmbH, Mario Emmenlauer      Tel. Buero: +49-89-74677203
Balanstr. 43                   mailto: memmenlauer * biodataanalysis.de
D-81669 München                          http://www.biodataanalysis.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libgeotiff-1.4.2-cmake-use-BUILD_SHARED_LIBS.patch
Type: text/x-patch
Size: 2439 bytes
Desc: not available
Url : http://lists.maptools.org/pipermail/geotiff/attachments/20171209/f383d276/attachment.bin 


More information about the Geotiff mailing list