fastled-wasm-compiler
The compiler and build system for FastLED for WASM.
# Option 1: Clone only main branch
git clone -b main --single-branch https://github.com/zackees/fastled-wasm-compiler.git
# Option 2: Clone normally then configure to exclude gh-pages
git clone https://github.com/zackees/fastled-wasm-compiler.git
cd fastled-wasm-compiler
git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/* ^refs/heads/gh-pages"
Development
Run ./install to install the dependencies.
Run ./lint to run the linter.
Run ./test to run the tests.
Thin Precompiled Headers (Thin PCH)
The FastLED WASM compiler now supports Thin Precompiled Headers (Thin PCH), which provide faster rebuild times and better cacheability compared to traditional PCH.
To enable Thin PCH:
- Set the
THIN_PCH=1environment variable - Or use the
--thin-pchflag with the build scripts
Example:
# Using environment variable
THIN_PCH=1 ./build_tools/build_lib.sh --all
# Using command line flag
./build_tools/build_lib.sh --thin-pch --all
Notes:
Metadata
Release files for fastled-wasm-compiler 1.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fastled_wasm_compiler-1.1.7-py3-none-any.whl | Python 3 | none | any | Details for fastled_wasm_compiler-1.1.7-py3-none-any.whl |
Release files / fastled_wasm_compiler-1.1.7-py3-none-any.whl
| Download URL | fastled_wasm_compiler-1.1.7-py3-none-any.whl |
|---|---|
| Size | 95.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e44dacabc0e0191c203dd366fbc371c37d16eb29f6dabb7e851ccf893066abcf
|
|
BLAKE2b-256 checksum How to use checksums |
718da8e523da52dc0cdcfbfd287184307f2f9c77779dfff016a23cffc587fcee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.5
|
Security for fastled-wasm-compiler 1.1.7
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.