Skip to content

Fix CoreFoundation.h header in standalone CF build #1690

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

Merged
merged 1 commit into from
Sep 12, 2018

Conversation

copumpkin
Copy link
Contributor

The SwiftRuntime header has a big warning in it saying not to use it unless you're building with the swift runtime, which this build.py doesn't do.

cc @millenomi

Also, as a related aside: does this CoreFoundation/build.py get exercised by @swift-ci? I couldn't find any information on how to affect its behavior but I'd love to add a skeleton build to avoid it getting broken in future

The SwiftRuntime header has a big warning in it saying not to use it
unless you're building with the swift runtime, which this build.py
doesn't do.
@parkera
Copy link
Contributor

parkera commented Sep 12, 2018

I don't think our CI has any way to trigger the standalone build. I'd love if it did, along with building for macOS, actually.

@parkera
Copy link
Contributor

parkera commented Sep 12, 2018

@swift-ci test and merge

@copumpkin
Copy link
Contributor Author

@parkera thanks! Is that something I could realistically do? I tried to figure out what it was doing but it looks like a jenkins config that is set up server-side and thus isn't something I could meaningfully affect from within the repo (like in a PR).

@swift-ci swift-ci merged commit c15c6f6 into swiftlang:master Sep 12, 2018
@parkera
Copy link
Contributor

parkera commented Sep 13, 2018

@shahmishal can you provide us some guidance on how we may go about updating the jenkins config?

@shahmishal
Copy link
Member

@parkera Did you want to update the current Linux PR job, or add new macOS job?

@parkera
Copy link
Contributor

parkera commented Sep 13, 2018

There are a few things. The first is to add a build of the Darwin build of swift-corelibs-foundation to our CI, so we know that it builds correctly when accepting PRs.

@shahmishal
Copy link
Member

@parkera I added support for macOS testing, once everything looks good I will add it to test and merge job too.

https://ci.swift.org/job/swift-corelibs-foundation-PR-macOS/2/console

@copumpkin
Copy link
Contributor Author

@shahmishal that looks awesome! I haven't quite figured out how those jenkins builds work yet: is that going to test the CoreFoundation/build.py or the root build.py? Or both? 😁

@shahmishal
Copy link
Member

shahmishal commented Sep 14, 2018

it's using build-script from apple/swift repository.

swift/utils/build-script -R -T --llbuild --swiftpm --xctest --debug-foundation -- --reconfigure --lit-args=-v

Looks like it might be using xcodebuild, it might not be building Foundation at all. -- https://github.com/apple/swift/blob/master/utils/build-script-impl#L2515

@millenomi
Copy link
Contributor

From my work on merging, it looks like you might want to expect some breakage. I’ll be on standby if that happens.

@copumpkin
Copy link
Contributor Author

@millenomi sorry, was that to me, or to Mishal about the CI stuff? If to me I actually pin to known-good revisions so I'll keep an eye out for it but it shouldn't be anything too pressing 😄

@millenomi
Copy link
Contributor

Yeah, sorry, the above was to @shahmishal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants