You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clang_Driver_getExternalActionsForCommand_v0 exists as a function to get a list of actions that would be performed given a set of clang driver arguments. However, it does not currently expand response files, which is a difference between it and the real clang driver.
This means that response files get treated as inputs, I believe, and passed on to other actions. (For instance, a response file with -Wl,<arg> gets passed as-is to the linker, which causes it to fail because the linker doesn't understand -Wl.)
clang_Driver_getExternalActionsForCommand_v0 should be updated to expand response files.
The text was updated successfully, but these errors were encountered:
…lActionsForCommand_v0.
This is necessary because build systems like SwiftBuild may pass arguments to the Clang driver via response files.
Without this, the response files are treated as inputs and passed along to the external actions themselves, which is incorrect.
This resolvesswiftlang#10441.
clang_Driver_getExternalActionsForCommand_v0
exists as a function to get a list of actions that would be performed given a set of clang driver arguments. However, it does not currently expand response files, which is a difference between it and the real clang driver.This means that response files get treated as inputs, I believe, and passed on to other actions. (For instance, a response file with
-Wl,<arg>
gets passed as-is to the linker, which causes it to fail because the linker doesn't understand-Wl
.)clang_Driver_getExternalActionsForCommand_v0
should be updated to expand response files.The text was updated successfully, but these errors were encountered: