Better autogen

[ShiCheng-Lu]

change the autogen to be called only once to generate all the can files for one project

autogenner -f {source_dir} -t {all source templates...} -f {header dir} -t {all header templates}

changed test_runner auto-generator to use jinja

added a python template to generate some cansend functions for can (just preliminary)

[ShiCheng-Lu]

there are two uv_cutoffs, from power-distribution and uw_cutoff, both to telemetry, and autogen can't handle this, so slight name change. Previously, one of them is just ignored, but this is in fact a different message with different id.

[ShiCheng-Lu]

autogen will now read all board yamls once, all necessary message info is stored in this dictionary (list of boards to generate board id, and list of messages which is then filtered by the board at jinja generation)

[JarvisWeng]

Makes sense

[ShiCheng-Lu]

got rid of -y option, can't get rid of -b option unless we want to infer the board from the output path, which is a bit ugly. Maybe later with better_better_autogen

[ShiCheng-Lu]

this bit filters the messages to contain only the relevant ones for the specific board.

[ShiCheng-Lu]

there are some python lint issues in this library, it's annoying to fix, make a ticket for this.

[ShiCheng-Lu]

eventually, I want to have all autogeneration stuff in one place, for can autogen, test auto gen, and new project autogen.

better_better_autogen:

something like

-autogen
    - can
        - src
            - {{board}}_tx.c.jinja
            - {{board}}_rx.c.jinja
        - inc
            - {{board}}_struct.h.jinja
            - ...
    - test
        - test_runner.c.jinja
    - new_project
        - config.json
        - src
            - main.c
        - inc
      ....

then specifying autogen can -o <folder> will generate all the templates in the can folder into the output folder. each folder will possibly have some function that retrieves the data needed to generate it.

[JarvisWeng]

Makes sense