eb1f268654
Bumped UniFFI to 0.28.2 Added a tool to run uniffi-bindgen in library mode. It can input either a specific library path or the megazord crate name. Use that simplify several build scripts -- especially the generate docs ones. The best part of this is that we no longer have to maintain hand-written modulemaps, which makes adding a new component harder than it needs to be. Split out the uniffi-bindgen commands from `build-xcframework.sh`. This way you can run them standalone and see the results, even if you don't have XCode setup. One change is that automation/swift-components-docs/generate-swift-project.sh now uses `megazord_ios` rather than `megazord`. I think this should result in slightly more accurate docs, since historically some components in the Android megazord aren't in the iOS one (Although, I think they match at the present). |
||
|---|---|---|
| .. | ||
| embedded-uniffi-bindgen | ||
| nimbus-gradle-plugin | ||
| protobuf-gen | ||
| start-bindings | ||
| uniffi-bindgen-library-mode | ||
| README.md | ||
| build-book.sh | ||
| clean-gradle-autopublish.py | ||
| clean.py | ||
| dependency_summary.py | ||
| loc_summary.py | ||
| protobuf_files.toml | ||
| regenerate_dependency_summaries.sh | ||
| requirements.in | ||
| requirements.txt | ||
| update-moz-central-vendoring.py | ||
README.md
Miscellaneous Tooling Bits for Application Services
This directory contains miscellaneous tooling scripts that developers may need to run locally while working on application-services. You'll need to read the individual files to find out what they're for.
Some of the tools here are written in Python, and to run them you'll need
to install the Python dependencies listed in requirements.txt, like this:
pip3 install --require-hashes -r ./tools/requirements.txt
These dependencies are pinned to a specific hash for security. To update the versions of a dependency you will need to:
- Visit https://pypi.org/ and search for the target package.
- Download the
.tar.gzrelease bundle corresponding to the new version. - (In theory you'd audit the downloaded package to check that it's trustworthy, but realisitically we don't have good advice on how to do that effectively).
- Run
pip hash ./path/to/package.tar.gzto generate the hash string. - Update
requirements.txtwith the new version number and hash string.