Kaspar Schleiser

add ld-memory

9

This adds [ld-memory](https://github.com/kaspar030/ld-memory), a utility I wrote that creates GNU ld MEMORY sections from command line parameters. Needed for https://github.com/RIOT-OS/RIOT/pull/19692. (adds ~800kB to the image)

ci: tracking: migrate to github merge trains

4

This issue tracks the migration to github merge trains. Will update as we go along. - [x] make murdock build merge train branches #20052 - [x] create branch `merge_queue_migration`, try...

E.g., the riot-rs Cargo link-only "apps" don't invoke custom build rules for any selected modules.

refactor: model (parts of) Context via associated module

3

This enables some nifty features: - [ ] allow modules to define Rules - [ ] allow modules to define Tasks - [x] conflict a context This also implies that...

Use cases: - blobs - generated sources, e.g., turn a `something.proto` into source code that then gets compiled These can already be expressed using custom build rules, but IMO that's...

At least, - [ ] git - [ ] local path Nice to have: - [ ] git shortcuts - [ ] gh:org/repo - [ ] gl:org/repo - [ ]...

Current sketch: - `tasks:` added to a module - every module that defines a task implicitly `provides_unique` a magic name, e.g., `::task::`

feat: task dependencies

1

Tasks could have dependencies. E.g., a "run-with-qemu" task could depend on a "qemu-config" module, and only be available if that module is.

Currently, all dependency resolution is within one app/builder pair. There are use cases for crossing that boundary: - an application might want to build with a previously built library -...

Currently, laze uses - **context** - **builder**: maybe change to "target"? Is that ambiguous with a "make target" (or "ninja target", which refers to a build output? - **apps**: not...