-
Notifications
You must be signed in to change notification settings - Fork 2k
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
docker: don't export KCONFIG_ADD_CONFIG variable #17993
docker: don't export KCONFIG_ADD_CONFIG variable #17993
Conversation
Well, this is another thing that wasn't caught in #17396, exporting this variable always prevents the usual remapping from RIOTBASE->DOCKER_RIOTBASE to take place. I think the first way of addressing it is simply removing it from the list of exports https://github.com/fjmolinas/RIOT/blob/be7b8179d0a10680fda5d87b4a10697391a02777/makefiles/docker.inc.mk#L90. To properly fix it we would need to capture those But I'm also getting another issue:
|
Do you have this issue when removing |
Yes but I think its unrelated to this PR |
6aeac57
to
6e69943
Compare
Thanks @fjmolinas ! Dropping |
I pushed that change in replacement of the previous version and updated the PR title. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
6e69943
to
23b393e
Compare
Contribution description
When using
TEST_KCONFIG=1
along withBUILD_IN_DOCKER=1
to build some test applications, the builds fails with this kind of error (here withtests/shell
):make: *** No rule to make target '/work/riot/RIOT/tests/test_utils.config', needed by '/data/riotbuild/riotbase/tests/shell/bin/native/generated/out.config'
This PR fixes the problem by using the docker path to
tests_utils.config
when usingBUILD_IN_DOCKER=1
.I don't know if that's the better fix but that works.
Testing procedure
Run
TEST_KCONFIG=1 BUILD_IN_DOCKER=1 make -C tests/shell --no-print-directory
On master, you would get this:
With this PR, it builds fine:
Issues/PRs references
Found in #17992 when trying to build some cpp test application for esp32 with both TEST_KCONFIG and BUILD_IN_DOCKER enabled (I don't have the esp32 toolchain installed on my machine).