-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Link swift-ide-test
against the new (early)swift-driver and exercise its getSingleFrontendInvocationFromDriverArguments
C API
#75840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
f9b24d1
to
28a7f4f
Compare
a76378a
to
2bceadb
Compare
swift-ide-test
against earlyswiftdriver
and using its tooling libraryswift-ide-test
against the new (early)swift-driver and exercise its getSingleFrontendInvocationFromDriverArguments
C API
1 similar comment
@swift-ci test |
1 similar comment
@swift-ci test |
2bceadb
to
db93ed7
Compare
@swift-ci test |
db93ed7
to
400e9eb
Compare
@swift-ci test |
1 similar comment
@swift-ci test |
400e9eb
to
10b66da
Compare
@swift-ci test |
…e its 'getSingleFrontendInvocationFromDriverArguments' API This lays the groundwork for what it takes to start using the new driver's C API from compiler products such as SourceKit
…id conflict with the new driver's corresponding entry
…tionFromDriverArgumentsV3` This is the most recent version of the API.
To function properly in "in-process" mode `swift-driver` requires all swift scanner symbols to be present in the binary to be discoverable by dlsym.
@swift-ci please test |
@swift-ci please test Windows platform |
set(SwiftDriver_DIR | ||
"${CMAKE_BINARY_DIR}/../earlyswiftdriver-${SWIFT_HOST_VARIANT}-${SWIFT_HOST_VARIANT_ARCH}/${driver_package_configuration_dir}/cmake/modules/") | ||
set(TSC_DIR "${CMAKE_BINARY_DIR}/../earlyswiftdriver-${SWIFT_HOST_VARIANT}-${SWIFT_HOST_VARIANT_ARCH}/${driver_package_configuration_dir}/dependencies/swift-tools-support-core/cmake/modules/") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, FetchContent
or find_package
should be what we use here instead of hard-coding these paths.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well technically we are doing a find_package
, just setting SwiftDriver_DIR
beforehand 😅. We currently set SWIFT_EARLY_SWIFT_DRIVER_BUILD
, I'm not entirely clear why we're not just setting SwiftDriver_DIR
though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
set_property( | ||
TARGET swift-ide-test | ||
APPEND PROPERTY INSTALL_RPATH "${CMAKE_BINARY_DIR}/../earlyswiftdriver-${SWIFT_HOST_VARIANT}-${SWIFT_HOST_VARIANT_ARCH}/${driver_package_configuration_dir}/lib/" | ||
) | ||
set_property( | ||
TARGET swift-ide-test | ||
APPEND PROPERTY INSTALL_RPATH "${CMAKE_BINARY_DIR}/../earlyswiftdriver-${SWIFT_HOST_VARIANT}-${SWIFT_HOST_VARIANT_ARCH}/${driver_package_configuration_dir}/dependencies/swift-tools-support-core/lib/" | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely don't want an absolute INSTALL_RPATH. I would have also thought that this isn't needed regardless - the lib to be in the same place as swift-syntax, which is already on the rpath.
This lays the groundwork for what it takes to start using the new driver's C API from compiler products such as SourceKit
Using: swiftlang/swift-driver#1679