When running existing applications on macOS 11 systems (through beta 6, Intel, clean installs), I've noticed that many of the libraries that had .tbd files in versions of the macOS SDK as recent at 10.15 do not have corresponding .dylibs in /usr/lib in macOS 11.
The result of running our applications that expect these libraries is an immediate crash.
Considering that some of these libraries have been linkable under versions of macOS for years and are pretty important for the use of third-party libraries (such as libcurl, libxml2, libpq, libxslt) it seems odd that a decision would be made to remove these without warning.
Somewhat ironicaly, libpython2.7 is still there despite 2.7 now being out of support and Apple having announced some time ago that they'd be removing support for "scripting languages" in future versions of the OS. Not that I'm complaining, although on the basis of the stated removal, we have included our own copy of libpython for internal use, since we had fair warning from Apple.
Any suggestions? Anyone else having problems with this?
The result of running our applications that expect these libraries is an immediate crash.
Considering that some of these libraries have been linkable under versions of macOS for years and are pretty important for the use of third-party libraries (such as libcurl, libxml2, libpq, libxslt) it seems odd that a decision would be made to remove these without warning.
Somewhat ironicaly, libpython2.7 is still there despite 2.7 now being out of support and Apple having announced some time ago that they'd be removing support for "scripting languages" in future versions of the OS. Not that I'm complaining, although on the basis of the stated removal, we have included our own copy of libpython for internal use, since we had fair warning from Apple.
Any suggestions? Anyone else having problems with this?
