Can a user bring their own memory.x about rp-hal HOT 5 CLOSED

See #156 for rationale for #158

from rp-hal.

Can we control the copying of the memory.x file with a feature flag?

rp-hal = { version = "1.0", features=["no_memory_file"] }

from rp-hal.

The BSP would set it on the HAL. A project can set it on the BSP if it so chooses.

from rp-hal.

OK, so after half a day of trying I'm going to abandon this as "non-trivial". Case in point:

If you build in a workspace, the features set on the HAL by the BSPs also apply to the HAL's only examples. If you build just the HAL by itself, the BSPs cannot set features on the HAL.

from rp-hal.

Agreed, this is not worth the effort.
Closing this issue since #158 was closed without merging .

from rp-hal.