Skip to content
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

Modify handling of platform site to allow for venv usage #246

Merged
merged 1 commit into from
Feb 14, 2025

Conversation

freakboy3742
Copy link
Member

Modifies how the support package handles the "platform site".

Previously, the platform site was a location that could be placed on the PYTHONPATH to make an environment appear to be an iOS environment. It uses a siteconfigure.py file to achieve this.

This PR preserves this usage; but also adds a make_cross_venv.py script. If you invoke this script, providing the location of a macOS virtual environment, that virtual environment will be modified (by adding some files to the site packages folder) in such a way that the virtual environment will appear to be an iOS environment. In addition, if build is invoked in that environment, the isolated venv created as part of that build will also appear as an iOS environment.

The location of the folder has been moved into the XCframework itself, so that the framework slices have readily access to the platform configuration for that slice of the framework. The names have also been modified to use the multiarch naming for each slice, rather than a name derived from the makefile naming conventions.

PR Checklist:

  • All new features have been tested
  • All new features have been documented
  • I have read the CONTRIBUTING.md file
  • I will abide by the code of conduct

@freakboy3742
Copy link
Member Author

Currently failing CI because beeware/briefcase#2155 is required to adapt to the iOS platform-config changes.

@freakboy3742 freakboy3742 merged commit c82aa70 into main Feb 14, 2025
5 checks passed
@freakboy3742 freakboy3742 deleted the platform-config branch February 14, 2025 02:19
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.

1 participant