[libc++] Segregate back-deployment dylibs into their own subdirectory
authorLouis Dionne <ldionne@apple.com>
Fri, 15 May 2020 16:13:48 +0000 (12:13 -0400)
committerLouis Dionne <ldionne@apple.com>
Fri, 15 May 2020 16:16:02 +0000 (12:16 -0400)
commitbb7191aa81b858e9c979556eca55a7bc0db2d87b
treeeff7a5d13882ba7f1d938017c5c2c1115f11b29c
parent4ec340c3e99c7fa4789387452864ad3cf36ab579
[libc++] Segregate back-deployment dylibs into their own subdirectory

Otherwise, specifying (for example) the libc++.dylib from macos10.13
but the libc++abi.dylib from macos10.12 would end up adding library
paths for both the 10.12 and 10.13 dylibs, which would each contain
a copy of both libc++abi.dylib and libc++.dylib. By using a separate
directory for libc++.dylib and libc++abi.dylib, those do not conflict
anymore.

The back-deployment roots were updated to match this change.
libcxx/utils/ci/macos-backdeployment.sh