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

Setting custom BOARD_ROOT raises FileNotFoundError #32699

Closed
5frank opened this issue Feb 26, 2021 · 1 comment
Closed

Setting custom BOARD_ROOT raises FileNotFoundError #32699

5frank opened this issue Feb 26, 2021 · 1 comment

Comments

@5frank
Copy link

5frank commented Feb 26, 2021

for maybe_board in (boards / arch).iterdir():

above fails with error FileNotFoundError: [Errno 2] No such file or directory: when trying to set custom BOARD_ROOT to a directory that do not have all arches.
This would fix it, but not sure if setting BOARD_ROOT is deprecated or bad practice?

 def find_arch2board_set_in(root, arches):
     ret = defaultdict(set)
     boards = root / 'boards'
 
     for arch in arches:
-        for maybe_board in (boards / arch).iterdir():
+        arch_dir = (boards / arch)
+        if not arch_dir.is_dir():
+           continue
+        for maybe_board in arch_dir.iterdir():
             if not maybe_board.is_dir():
                 continue
             for maybe_defconfig in maybe_board.iterdir():

I am also curious why the west --board option can not be a path? It seems to me that having a unique identifier string for every board will cause conflicts and limits the use of sub-directories like zephyr/arm/nucleo/<model>.

@5frank
Copy link
Author

5frank commented Feb 26, 2021

This was caused by a incorrectly configured build environment.

@5frank 5frank closed this as completed Feb 26, 2021
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

No branches or pull requests

1 participant