You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Felix "xq" Queißner 4480b7c17a Fixes build script enough to make next-gen example build. 8 months ago
.github/workflows Deduplicates info in github ci script. 8 months ago
board-support Fixes build script enough to make next-gen example build. 8 months ago
build Fixes build script enough to make next-gen example build. 8 months ago
core Fixes build script enough to make next-gen example build. 8 months ago
examples Fixes build script enough to make next-gen example build. 8 months ago
for-extraction/uf2-flasher Refactors packaging process from bash to python 9 months ago
tools Fixes build script enough to make next-gen example build. 8 months ago
.envrc Refactors packaging process from bash to python 9 months ago
.gitattributes Initial vomit: not working at all, basic docs. 2 years ago
.gitignore Refactors packaging process from bash to python 9 months ago
README.md Makes examples/next-gen kinda build with experimental setup. Packages are now correct and microzig-build can determine all available targets and BSPs. 8 months ago
build.zig Makes examples/next-gen kinda build with experimental setup. Packages are now correct and microzig-build can determine all available targets and BSPs. 8 months ago
build.zig.zon Makes examples/next-gen kinda build with experimental setup. Packages are now correct and microzig-build can determine all available targets and BSPs. 8 months ago
flake.lock Refactors packaging process from bash to python 9 months ago
flake.nix Refactors packaging process from bash to python 9 months ago

README.md

MicroZig

Continuous Integration

Overview

  • core/ contains the shared components of MicroZig.
  • board-support/ contains all official board support package.
  • examples/ contains examples that can be used with the board support packages.
  • tools/ contains tooling to work on MicroZig.

Versioning Scheme

MicroZig versions are tightly locked with Zig versions.

The general scheme is ${zig_version}-${commit}-${count}, so the MicroZig versions will look really similar to Zigs versions, but with our own commit abbreviations and counters.

As MicroZig sticks to tagged Zig releases, ${zig_version} will show to which Zig version the MicroZig build is compatible.

Consider the version 0.11.0-abcdef-123 means that this MicroZig version has a commit starting with abcdef, which was the 123rd commit of the version that is compatible with Zig 0.11.0.

TODO (before exchanging upstream)