xbuild
xbuild is PEP 517 build frontend that has additions and extensions to support cross-compiling wheels for platforms where compilation cannot be performed natively - most notably Android and iOS. Initial experimental support also exists for Emscripten (WASM).
Quickstart
xbuild
Create a virtual environment for your build platform (i.e., the platform where you will be compiling), and install xbuild. Then, run xbuild from the root directory of the project you want to build. You must pass in the --sysconfig argument, providing the path to the sysconfig_vars JSON file for the target platform, or the equivalent sysconfigdata python configuration:
$ python3 -m venv venv
$ source venv/bin/activate
(venv) $ python -m pip install xbuild
(venv) $ python -m xbuild --sysconfig path/to/_sysconfig_vars__...json
This will do the equivalent of python -m build, but in an cross-platform environment that is pretending to be the environment described by the sysconfig data that has been provided.
xvenv
To explicitly create a cross-platform virtual environment, start by creating a virtual environment for your build platform (i.e., the platform where you will be compiling), then install and use the xvenv script to create cross-platform virtual environment, specifying the platform and architecture you want to target.
$ python3 -m venv venv
$ source venv/bin/activate
(venv) $ python -m pip install xbuild
(venv) $ python -m xvenv --platform ios --arch arm64-iphonesimulator x-venv
You can then activate and deactivate the x-venv environment as you would any other virtual environment.
Documentation
Documentation for Toga Chart can be found on Read The Docs.
Community
xbuild is part of the BeeWare suite. You can talk to the community through:
We foster a welcoming and respectful community as described in our BeeWare Community Code of Conduct.
Contributing
If you experience problems with xbuild, log them on GitHub. If you want to contribute code, please fork the code and submit a pull request.
Release files for xbuild 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| xbuild-0.3.0.tar.gz | 88.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xbuild-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 111.1 kB
Release files / xbuild-0.3.0.tar.gz
| Download URL | xbuild-0.3.0.tar.gz |
|---|---|
| Size | 88.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67bc67081c2a716c832e15dd7fab26fcfa9da0647d57a2886dd2881c4f6564f9
|
|
BLAKE2b-256 checksum How to use checksums |
33ba1c5fece522fa20277d630ba56dacc5716e836ac3d1bdedae6723dc5d70e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / xbuild-0.3.0-py3-none-any.whl
| Download URL | xbuild-0.3.0-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d14b3239557bfd70aa546b735837bf287355c8d91fe3b396bae92ff9e2d0a73
|
|
BLAKE2b-256 checksum How to use checksums |
2ea5750b2954862948b0c7cd2482c5fbd9a11ca39d8d622f0cf8a64b895287f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log