ElicMagus
/
microzig
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
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.
411 Commits
2 Branches
0 Tags
12 MiB
Zig 79.9%
C 14.6%
Assembly 3.9%
HTML 0.8%
Nix 0.4%
Other 0.3%
 
 
 
 
 
 
main
wch-ch32v003
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '31f26f57d9'
${ noResults }
Go to file
Felix "xq" Queißner 31f26f57d9 Refactors packaging process from bash to python 8 months ago
.github/workflows Fixes GitHub CI 9 months ago
board-support Refactors packaging process from bash to python 8 months ago
build Refactors packaging process from bash to python 8 months ago
core Refactors packaging process from bash to python 8 months ago
examples Snapshot for transfer 9 months ago
for-extraction/uf2-flasher Refactors packaging process from bash to python 8 months ago
tools Refactors packaging process from bash to python 8 months ago
.envrc Refactors packaging process from bash to python 8 months ago
.gitattributes Initial vomit: not working at all, basic docs. 2 years ago
.gitignore Refactors packaging process from bash to python 8 months ago
README.md Adds CI to readme. 9 months ago
build.zig Refactors packaging process from bash to python 8 months ago
build.zig.zon Refactors packaging process from bash to python 8 months ago
flake.lock Refactors packaging process from bash to python 8 months ago
flake.nix Refactors packaging process from bash to python 8 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)