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.
main
wch-ch32v003
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '37319a93ca'
${ noResults }
microzig/docs/hardware_support_packages.adoc

8 lines
384 B
Plaintext
Raw Normal View History Unescape Escape

Mimic new stdlib build API (#111) * start on new docs to match api * tweak the MicroZig dependency tree * use microzig_options * remove empty.zig * add test programs * keep it to one arch, bump flash for debug
2 years ago
= Hardware Support Packages
:imagesdir: images
:toc: macro
toc::[]
Fix typos (#113)
2 years ago
This document goes over the _suggested_ way to structure a hardware support package. At the end of the day, MicroZig is designed for flexibility, we do not require all "supported" hardware be defined in one monorepo. Instead, we make it so that you can define your hardware locally if that best suits your project.