[XERCESC-2176] Incorrect symbolic links created for Linux static library and MacOS static and shared libraries

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.2.0, 3.2.1, 3.2.2
• Fix Version/s: 3.2.3, 4.0.0
• Component/s: Build
• Environment: Linux, MacOS
• Assignee: Roger Leigh
• Reporter: Brent Davis
• Created: 23/Aug/19 18:30
• Updated: 10/Oct/22 14:07
• Resolved: 03/Apr/20 06:54

Description

We build Xerces-C++ for both the Linux and MacOS platforms, with both static and shared libraries.  There are arguably some dubiously named symbolic links created by src/CMakeLists.txt.  The symlinks are always named 'libxerces-c.so' regardless or library type, or use of the .dylib extension on MacOS.

Platform	Library Type	Symbolic Link	Comment
Linux	static	libxerces-c.so -> libxerces-c-3.2.a	symbolic link should either be libxerces-c.a or not created
	shared	libxerces-c.so -> libxerces-c-3.2.so	good
MacOS	static	libxerces-c.so -> libxerces-c-3.2.a	symbolic link should either be libxerces-c.a or not created
	shared	libxerces-c.so -> libxerces-c-3.2.dylib	symbolic link should best be named libxerces-c.dylib

Curiously, the Microsoft vcpkg folks just recently ran into the Linux static library portion of this issue and elected to not create the symlink in that case.  See [[xerces-c] produces strange files in installed/x64-linux/lib|https://github.com/microsoft/vcpkg/issues/7490].