-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[python] Split Python wheel in two separate wheels #20700
Merged
andy31415
merged 1 commit into
sve
from
cherry-pick-61dd4d020479ad877ee7010941cfc615b6fa1a86
Jul 14, 2022
Merged
[python] Split Python wheel in two separate wheels #20700
andy31415
merged 1 commit into
sve
from
cherry-pick-61dd4d020479ad877ee7010941cfc615b6fa1a86
Jul 14, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Move package information into manifest file * Specify scripts in manifest as well * Make build-chip-wheel.py independent of build variant Pass library name via command line arguments. This makes build-chip-wheel.py more generic. * Move package requirements to manifest file as well * Split Python into library and repl package * Introduce common GN template chip_python_wheel_action * Add runtime dependency between chip-repl and chip-library * Split chip-library into chip-core and chip-clusters * Apply restyled * Install all wheels for unit tests * Use new chip-repl build target * Fix Cirque failures * Fix wheel names for chip_clusters/chip_repl
PR #20700: Size comparison from 0390a8d to c5f1670 Increases (4 builds for cc13x2_26x2, cyw30739, esp32)
Decreases (7 builds for bl602, cc13x2_26x2, cyw30739, nrfconnect, telink)
Full report (32 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
andy31415
deleted the
cherry-pick-61dd4d020479ad877ee7010941cfc615b6fa1a86
branch
July 14, 2022 13:04
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Currently the Python Controller library is one large wheel, with the native library, the clusters, the interaction model and the REPL packed in a single wheel.
This PR is a first step in break out the library into smaller wheels.
Change overview
The first few commits aim to make the current wheel build logic more generic by moving most wheel specific information into
BUILD.gn
. Then this splits it in two wheels: The main wheel namedchip-library
(still fairly monolithic, with cluster library and interaction model in a single wheel), and achip-repl
, with the REPL and its dependency.This lowers the dependency of
chip-library
already. I also plan to split the fairly independent cluster library into a separate wheel in a follow up PR.Testing
Build and runtime tested locally (using
scripts/build_python.sh -m minimal -i separate
andchip-repl
).