Hi. Xcode 16 adds a new check to validate that the linking dynamic library doesn't attempt to link against a library with its own install name. This happens in this library in a couple of build scripts where the K/N framework links against the CocoaPods built framework with the same install name. The issue should be reproducible with e.g.:
Is there a particular reason why K/N frameworks in this library have the same name as the frameworks they link against? If these frameworks are only used as a linkage test, would it make sense to rename these (renaming will implicitly change the install name):
Hi. Xcode 16 adds a new check to validate that the linking dynamic library doesn't attempt to link against a library with its own install name. This happens in this library in a couple of build scripts where the K/N framework links against the CocoaPods built framework with the same install name. The issue should be reproducible with e.g.:
Is there a particular reason why K/N frameworks in this library have the same name as the frameworks they link against? If these frameworks are only used as a linkage test, would it make sense to rename these (renaming will implicitly change the install name):