-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get setting default values from settings.yaml #6595
Get setting default values from settings.yaml #6595
Conversation
Arch Linux :-( $ arm-none-eabi-gcc -dumpversion
|
Above error seems target dependent, in this case MATEKF765 |
8870ab8
to
3ae27bf
Compare
931a65a
to
5087026
Compare
Interesting that we now get linker warnings on some (non -Os?) platforms:
|
More interesting, shortGitRevsion not passed to the FC
|
And if I build the same target with Seems like we still have some issues here. |
Strange, I don't see this warning EDIT: This seems to be related to your |
Also seeing strange
|
Indeed, with gcc 9.3 I don't get any build warnings relating to
|
(erroneous comment deleted) |
@shellixyz finally got to the bottom of the
|
This appear to be due to the reordering of CMakeList.txt, such that Moving the Git stuff before |
ba75b97
to
b21814c
Compare
Looking good. |
- Add support for resolving types and values in multiple compilers - Add support for resolving types and values in clang 10 - Add support for using the host compiler for resolving the settings This allows us to run the generator for the unit tests, since they now need the settings_generated.h file to get the default setting values from it.
392242e
to
438dd40
Compare
Great work! Thanks |
I checked the default are the same as before, nothing has changed