Skip to content
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

nrf: Shrink "<peripheral> does not exist" error messages. #4009

Closed
wants to merge 1 commit into from

Conversation

aykevl
Copy link
Contributor

@aykevl aykevl commented Aug 2, 2018

Code size reductions:
nrf51: -132
nrf52: -188

Code size reductions:
nrf51: -132
nrf52: -188
@dpgeorge
Copy link
Member

dpgeorge commented Aug 4, 2018

I think for ports that are tight on flash this is a good optimisation. You can even go a bit further and use "doesn't" instead of "does not".

For cases where there is enough flash (eg nrf52840) it might be nice to have more informative messages, which can be controlled via MICROPY_ERROR_REPORTING_DETAILED, but it's probably not worth the effort to provide such configurability right now.

@dpgeorge
Copy link
Member

Merged in 4e1c2fc with "does not" replaced with "doesn't".

@dpgeorge dpgeorge closed this Jan 31, 2019
tannewt added a commit to tannewt/circuitpython that referenced this pull request Sep 7, 2021
This uses a step output from the test job to set the build matrix
for the board build jobs. The built boards depends on which files
were changed.

* Changes contained within ports/*/boards/ will build each board.
* Changes contained within ports/* will build all boards from the
  port.
* All other file changes will build all boards.

All boards will be build for pushes in `adafruit/circuitpython` as
well.

A side-effect is that we no longer need to explicitly list the
boards to build. It will automatically update as new folders are
added.

Related to micropython#4009
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants