Closed
Description
Trying to make a custom build with the custom build action, I get a failure, with the following error:
Run make -j4 $FLAGS BOARD="$BOARD" DEBUG=$DEBUG TRANSLATION="$TRANSLATION"
make -j4 $FLAGS BOARD="$BOARD" DEBUG=$DEBUG TRANSLATION="$TRANSLATION"
shell: /usr/bin/bash -e {0}
env:
pythonLocation: /opt/hostedtoolcache/Python/3.13.2/x64
PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.13.2/x64/lib/pkgconfig
Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.2/x64
Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.2/x64
Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.2/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.13.2/x64/lib
TRANSLATION: en_US
BOARD: adafruit_feather_esp32s3_reverse_tft
FLAGS:
DEBUG: 0
make: *** No targets specified and no makefile found. Stop.
Error: Process completed with exit code 2.
This seems to be caused by #10026 which removed board-to-port from deps/ports/action.yml requiring instead to input the port, without adding a port entry in the custom action. Personally I would prefer NOT to add more complexity to the custom build action form and instead revert to the previous behavior, or to find the port as before if absent.