-
Notifications
You must be signed in to change notification settings - Fork 440
Move additional swift compiler flags from build-script to Package.swift #162
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
Conversation
a006c16
to
5d58ab6
Compare
Thanks for all your feedback. I have updated the PR to only specify the unsafe flags when we are in a controlled CI environment, i.e. if @swift-ci Please test |
Build failed |
@swift-ci Please test |
Build failed |
@swift-ci Please test |
Build failed |
@swift-ci Please test |
I have modified this PR to only contain unsafe flags when we are in a controlled CI environment, i.e. if the environment variable Could you please take another look at the changes? |
5d58ab6
to
032a456
Compare
This allows for a more consistent build, independent of whether build-script was used or not. This will allow us to use a unified build directory for all packages depending on Swift later on.
032a456
to
c1209f6
Compare
@swift-ci Please test |
Add `ignore-unparsable-files` to silence diagnostics for invalid syntax
Moving all additional Swift compiler flags from
build-script.py
toPackage.swift
allows for a more consistent build, independent of whether build-script was used or not.This will allow us to use a unified build directory for all packages depending on Swift later on.