[riot-notifications] [RIOT-OS/RIOT] BUILD_IN_DOCKER ignores USEMODULE (#14504)
notifications at github.com
Fri Sep 17 13:13:46 CEST 2021
I took some look at this and I think there is several ways to fix this.
First of all, the reason why `BINDIRBASE` and `USEMODULE` aren't added to `DOCKER_ENVIRONMENT_CMDLINE_AUTO` is because of their 'origin'. the Makefile origin function tells us that BINDIRBASE is "override" and USEMODULE is "file".
Thus, the filter command discards them because it expects them to come from either environment or command.
A quick fix to` BINDIRBASE` would be this:
>From db618cd9ace847b2ef3b5b8b928a5fc79ed746b7 Mon Sep 17 00:00:00 2001
From: Dylan Laduranty <dylan.laduranty at mesotic.com>
Date: Fri, 17 Sep 2021 13:10:55 +0200
Subject: [PATCH] tmp
Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile.include b/Makefile.include
index 3ca75ca268..b14cc047cc 100644
@@ -139,7 +139,7 @@ override RIOTTOOLS := $(abspath $(RIOTTOOLS))
override RIOTPROJECT := $(abspath $(RIOTPROJECT))
override APPDIR := $(abspath $(APPDIR))
override BUILD_DIR := $(abspath $(BUILD_DIR))
-override BINDIRBASE := $(abspath $(BINDIRBASE))
+override BINDIRBASE ?= $(abspath $(BINDIRBASE))
override BINDIR := $(abspath $(BINDIR))
override PKGDIRBASE := $(abspath $(PKGDIRBASE))
override DLCACHE_DIR := $(abspath $(DLCACHE_DIR))
But I am really unsure about all the side effects...
Regarding `USEMODULE`, a quick fix is to call make with -e flag which will enforce the environnement override so the filter function will now see USEMODULE origin as "environnement override" again this might have side effects I am unaware
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications