Skip to content

Non-Darwin SDKs product results in per-arch directories. #1710

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

Closed
wants to merge 1 commit into from

Conversation

drodriguez
Copy link
Contributor

Depends on swiftlang/swift#19432

Unix (other than Darwin) and Windows do not support fat binaries.
However, the build system was placing the build results in the
platform/OS folder, instead of the per-architecture folder. Having two
architectures side by side was impossible.

After applying the above patch in the Swift compiler, non-Darwin
platforms will look into the per-architecture folders, so the sibling
projects need to leave the products in the right place.

The change is performed in the CMakeList.txt file (which as far as I
understand is not used to build Foundation at the moment), and the
Python script.

@millenomi
Copy link
Contributor

I will trigger testing on this as needed when the main patch has been vetted.

@compnerd
Copy link
Member

I think that we should split this up into two changes. The CMake changes can go in first since they aren't in use just yet.

@drodriguez
Copy link
Contributor Author

The CMake is probably not use by “anyone” at the moment. The script is the real thing, sadly. Splitting it is not a problem, the CMake changes should not affect the build at all.

Depends on swiftlang/swift#19432

Unix (other than Darwin) and Windows do not support fat binaries.
However, the build system was placing the build results in the
platform/OS folder, instead of the per-architecture folder. Having two
architectures side by side was impossible.

After applying the above patch in the Swift compiler, non-Darwin
platforms will look into the per-architecture folders, so the sibling
projects need to leave the products in the right place.
@drodriguez
Copy link
Contributor Author

I left in this PR the changes in the script. I will create another PR with the CMake changes. We know (because Jenkins passed in the dependent PR) that this changes work and should be enough for most people.

@alblue
Copy link
Contributor

alblue commented Nov 8, 2018

@swift-ci please test linux

@drodriguez drodriguez closed this Oct 3, 2019
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.

4 participants