Closed RICCIARDI-Adrien closed 9 months ago
Hi @jlbirccyn, this PR is now ready for review (if you have time to).
Hi @jlbirccyn, what do you think about this PR ?
Thanks for the feedback, I will change it. So it's always make.py
in all Trampoline, that's correct ?
So it's always
make.py
in all Trampoline, that's correct ?
Yes, to build an OSEK/AUTOSAR application, but to build goil, it's build.py
make.py calls build.py
When you run goil for the first time, make.py and build.py are generated. make.py manages dependencies on the oil file. If you modify the oil file, make.py runs goil and goil generates a new build.py file which is then called by make.py to manage the rest of dependencies. This is why there is 2 scripts.
Got it, thank you very much for the explanations !
I will put the proper make.py
in the future documentation for new applications.
I updated this PR accordingly.
It is merged !
Oups, except the .yaml files uses build.py instead of make.py. Could you do an update and a new PR to fix that ?
Nice catch ! Here is the PR, I replaced build.py
by make.py
for all AUTOSAR applications.
https://github.com/TrampolineRTOS/trampoline/pull/136
This PR adds all POSIX examples to the CI and also allows to fix some warnings discovered by the CI builds.