Skip to content

Local-module debug builds shadow boarddev with displaydev - #17

Merged
bdbarnett merged 2 commits into
mainfrom
env-to-boarddev
Oct 8, 2026
Merged

bdbarnett merged 2 commits into
mainfrom
env-to-boarddev

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

PyDevices/pydevices#131 moves the env helpers from displaydev to boarddev as a hard break, and displaydev now reads its PYDEVICES_* settings through boarddev. With --local-modules, this build put a local displaydev over the TestPyPI pydevices, so a new displaydev would have met an old boarddev that has no env_int. The debug sync now copies boarddev.py beside displaydev, and the default build removes it with the other shadows.

While I was there I fixed one more thing: usdl2.py is read from pydevices/utils/, where it lives now. The old drivers/ path made the debug sync skip it.

Merge order: after PyDevices/pydevices#131. The default build (no --local-modules) is unaffected either way.

Tested: I ran sync_android_display_modules and clear_android_local_module_shadows against #131's checkout and a scratch APP_DIR. Both displaydev/ and boarddev.py were staged, then both were removed. bash -n is clean. I didn't build an APK.

displaydev reads its PYDEVICES_* settings through boarddev's env helpers
since pydevices moved them there (a hard break), so a local displaydev
over an older TestPyPI pydevices would fail on its first env read. The
debug sync copies boarddev.py beside it and the default build removes it.
usdl2 is read from pydevices/utils/, where it lives now.
@bdbarnett
bdbarnett merged commit 639645c into main Oct 8, 2026
1 check passed
@bdbarnett
bdbarnett deleted the env-to-boarddev branch October 8, 2026 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant