[Scons-users] Setting macOS shared library versioning information with scons

Ryan Schmidt scons at ryandesign.com
Tue May 8 12:40:16 EDT 2018


I'm a developer with the MacPorts package management system.

We noticed that after updating our scons port to 2.4.1, serf's shared library was built incorrectly, in that its current version and compatibility version were no longer being set. Here is our bug report about this:


It seems that scons's shared library generation code was refactored in 2.4.1, and in the process, the code that sets the -current_version and -compatibility_version flags was removed. Was this regression intentional, and if so, how are projects that use scons to build shared libraries on macOS now supposed to set library version information? Should they manually specify -current_version and -compatibility_version?

I realize scons 2.4.1 was released 2.5 years ago, but the problem remains in scons 3.0.1. The developers of serf are preparing to release serf 1.4.0, and I'm trying to help them ensure that they finally fix the shared library versioning issue on their end, hopefully in a way that's compatible with both current and future versions of scons.

More information about the Scons-users mailing list