1e1450bf5d
1. When one of the COMPONENT_DIRS points to a component directory (i.e. a directory containing component.mk, not a directory of multiple components), and there is a subdirectory in it which also contains a component, the subdirectory was mistakenly added to the list of components and compiled. For example: main/ component.mk main.c test/ component.mk test_main.c Would compile test_main.c and link libtest.a. 2. When one of the COMPONENT_DIRS points to a component directory, and the parent directory contained a directory with the same name as another component, that directory would be mistakenly added to the COMPONENT_PATHS. For example: esp/ esp-idf/ esp32/ (random stuff) mycomponent/ component.mk mycomponent.c myproject/ main/ Makefile and Makefile sets EXTRA_COMPONENT_DIRS=$(realpath ../mycomponent), then "esp32" directory which is at the same level as mycomponent was added to COMPONENT_PATHS. 3. If EXTRA_COMPONENT_DIRS pointed to a directory with a list of components, and one of the subdirectories was not a component, but had the same name as another component, than that directory would be mistakenly added to COMPONENT_PATHS instead of the real esp32 component directory. For example: my_components/ my_component/ component.mk my_component.c esp32/ (some random stuff) and EXTRA_COMPONENT_DIRS would point to my_components/, then "esp32" directory would be added to COMPONENT_PATHS instead of the real esp32 component directory. |
||
---|---|---|
.. | ||
apply_bot_filter.py | ||
build_examples.sh | ||
build_examples_cmake.sh | ||
check-executable.sh | ||
check_examples_cmake_make.sh | ||
checkout_project_ref.py | ||
configure_ci_environment.sh | ||
executable-list.txt | ||
get-full-sources.sh | ||
mirror-list.txt | ||
mirror-submodule-update.sh | ||
mirror-synchronize.sh | ||
push_to_github.sh | ||
setup_python.sh | ||
test_build_system.sh | ||
test_build_system_cmake.sh | ||
test_configure_ci_environment.sh |