Jeff Epler 3a68d2f621
Fix build error when frozen modules are updated
When a frozen module was added or updated, a build error would occur
during CI: `KeyError: 'FROZEN_MPY_DIRS'`.

In e40abda1bc I decided that it should be an error if all the expected
keys were not defined in the board settings dict. I made this change
and all seemed to be well; however, my testing did not exercise the
case that a frozen module was changed.

It turns out that FROZEN_MPY_DIRS was not being set in the board settings
dict because the output of print-FROZEN_MPY_DIRS was "FROZEN_MPY_DIRS ="
(which does not match the regular expression) instead of
"FROZEN_MPY_DIRS = " (with a trailing space).

This change fixes the problem by ensuring that an undefined or empty
variable still prints with a space character after the equal character.

Tested by running locally:
```
python3 -c 'import shared_bindings_matrix; print(shared_bindings_matrix.get_settings_from_makefile("ports/atmel-samd", "trinket_m0")["FROZEN_MPY_DIRS"])'
```
(prints a blank line, expected)

as well as simulating a change to the asyncio frozen submodule:
```
python3 -c 'import shared_bindings_matrix; print(shared_bindings_matrix.get_settings_from_makefile("ports/atmel-samd", "trinket_m0")["FROZEN_MPY_DIRS"])'
```
(which will build the elecfreaks_picoed board)
2023-11-18 09:43:36 -06:00
..
2023-09-20 11:23:39 -05:00
2023-11-14 21:20:03 -06:00
2023-09-20 11:23:39 -05:00
2023-10-24 14:48:02 -07:00
2023-10-24 14:48:02 -07:00
2023-09-22 14:25:23 -05:00
2023-09-22 13:39:24 -05:00
2023-11-08 09:08:10 -05:00
2023-11-08 09:08:10 -05:00
2023-11-14 21:20:03 -06:00
WIP
2023-10-25 21:24:52 +02:00
2023-10-26 15:30:42 -04:00
2023-10-26 19:39:26 +02:00
2023-10-26 19:39:43 +02:00
2023-10-23 20:14:40 -04:00
2023-10-25 11:44:32 -07:00
2023-09-22 13:51:57 -05:00
2023-09-22 13:51:57 -05:00
2023-08-01 13:50:05 -04:00
2023-10-23 20:37:42 -04:00