BuildPlan: infer -lc++ based on run-time triple
#6581
Conversation
Currently, when cross-compiling from Darwin to platforms that don't expect `-lc++` by default (e.g. most Linux distributions), the build will fail because `-lc++` is always passed. When should check the destination triple and not the host triple in the build plan code paths. rdar://107487090
|
@swift-ci smoke test |
There was a problem hiding this comment.
Honestly, I think that we should drop this entirely. The swift-driver has changed the behaviour for Darwin - it now uses clang as the linker driver. This is now something which we can control properly by using the driver. As long as we pass -enable-cxx-interop to the swift driver, it will correctly handle this - using clang++ to drive the linker which will add the C++ standard library to the linker invocation at the appropriate time. It also means that -Xclang-linker -stdlib= will do the proper thing.
This is unrelated to |
Cherry-pick of #6581 Currently, when cross-compiling from Darwin to platforms that don't expect `-lc++` by default (e.g. most Linux distributions), the build will fail because `-lc++` is always passed. When should check the destination triple and not the host triple in the build plan code paths. This leads to confusing build errors when cross-compiling more complex projects like Vapor. rdar://107487090
Currently, when cross-compiling from Darwin to platforms that don't expect
-lc++by default (e.g. most Linux distributions), the build will fail because-lc++is always passed. When should check the destination triple and not the host triple in the build plan code paths.This leads to confusing build errors when cross-compiling more complex projects like Vapor.
rdar://107487090
Modifications:
Modified
BuildPlan.swiftto check the value of thetripleproperty instead ofhostTriple. Added a test that verifies this cross-compilation case.Result:
Projects that contain C++ can now be cross-compiled from macOS to Linux.