Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Kartik K. Agaram 8e9ddaee55 . 8 months ago
..
termbox 7233 - fix some warnings from gcc 9 2 years ago
README.md 5868 3 years ago
browse_trace 5800 - move `browse_trace` to `tools/` dir 3 years ago
browse_trace.cc 5910 2 years ago
browse_trace.readme.md 7846 1 year ago
create_container 5891 2 years ago
expand_string_handle - 2 years ago
image-data . 9 months ago
linkify.cc 5799 - move html-generation to `tools/` directory 3 years ago
mu-init-minify.subx clean up treeshaking support for baremetal 8 months ago
regs.mu html: better highlighting for int registers 1 year ago
test_treeshake_translate 5796 - move treeshake to a new tools/ directory 3 years ago
translate_minified clean up treeshaking support for baremetal 8 months ago
treeshake.cc 5796 - move treeshake to a new tools/ directory 3 years ago
update_html . 8 months ago
update_signatures . 8 months ago
vga_palette 7842 - new directory organization 1 year ago
vga_palette.c 7842 - new directory organization 1 year ago
vga_palette.png 7842 - new directory organization 1 year ago

README.md

Run all these from the top-level mu/ directory.

Some tools for Mu's build process

These are built automatically.

  • enumerate: list numeric files in current directory, optionally --until some prefix.

Miscellaneous odds and ends

These are built lazily.

  • browse_trace: debugging tool. See browse_trace.readme.md for details.

  • linkify: inserts hyperlinks from variables to definitions in Mu's html sources. Hacky; just see the number of tests. Invoked by update_html.

  • treeshake_all: rebuild SubX binaries without tests and unused functions. Hacky; just helps estimate the code needed to perform various tasks.

    tools/treeshake_all
    

Notes to self: constraints on the tools/ directory

  • Don't overwhelm the initial view of the project with lots of crap in the root directory.
  • Directories go up top in the github view, so too many sub-directories are also overwhelming.
  • Don't increase increase build time too much; everything in tools/ shouldn't be automatically built.
    • stuff needed all the time is built from root directory.
  • tools/ contains many independent things; don't make it hard to see boundaries. Ideally just one source file per tool. If not, give related files similar name prefixes.