Open mbrossard opened 3 years ago
Can you share references of these in DAPlink, what they do and how ? I do not fully understand the usage of these in the applications.
Currently DAPLink uses wrapper shell scripts like:
They use wildcard for input and convention (firmware
) for outputs. This branch uses the name of current working directory to get the project name: https://github.com/mbrossard/DAPLink/blob/feature/compilers/tools/post_build_script_gcc.py
Looking at the
DAPLink
project it seems the different pre-build and post-build scripts have an implied calling convention: they should be called with a build directory named after the current project that needs to be 3 directories down from top-level with abuild
sub-directory with the binaries.I think the scripts should be given explicitly the different parameters:
I can see two implementation strategies: