Skip to contentSkip to conversation

tools: add a generic config for native tools building

PATCH New Otavio Salvador 2 participants 2 messages Dec 4, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tools: add a generic config for native tools building

The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine.

Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case).

Using this, we can package the tools doing:

$: make tools-all_defconfig
$: make tools-all

---

 configs/tools-all_defconfig | 3 +++
 tools/Makefile              | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)
 create mode 100644 configs/tools-all_defconfig
configs/tools-all_defconfig new file +3 -0
new file mode 100644
index 0000000000..be69bdf43a
@@ -0,0 +1,3 @@
+CONFIG_SYS_TEXT_BASE=0
+CONFIG_FIT=y
+CONFIG_FIT_SIGNATURE=y
tools/Makefile +1 -1
index c93d17a42f..29ff6ed221 100644
@@ -125,7 +125,7 @@ fit_info-objs   := $(dumpimage-mkimage-objs) fit_info.o
 fit_check_sign-objs   := $(dumpimage-mkimage-objs) fit_check_sign.o
 file2include-objs := file2include.o
 
-ifneq ($(CONFIG_MX23)$(CONFIG_MX28),)
+ifneq ($(CONFIG_MX23)$(CONFIG_MX28)$(CONFIG_FIT_SIGNATURE),)
 # Add CONFIG_MXS into host CFLAGS, so we can check whether or not register
 # the mxsimage support within tools/mxsimage.c .
 HOSTCFLAGS_mxsimage.o += -DCONFIG_MXS
Signature · 1 line
2.19.2
#1 lore raw

PATCH 1/1 tools: add a generic config for native tools building

Quoted 10 lines · Otavio Salvador

The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine.

Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case).

Quoted 6 lines

Using this, we can package the tools doing:

$: make tools-all_defconfig
$: make tools-all

The tools build for me across a number of architectures, the tools list is the same as 2018.09.

Thanks

Quoted 32 lines

---

 configs/tools-all_defconfig | 3 +++
 tools/Makefile              | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)
 create mode 100644 configs/tools-all_defconfig
configs/tools-all_defconfig new file +3 -0
new file mode 100644
index 0000000000..be69bdf43a
@@ -0,0 +1,3 @@
+CONFIG_SYS_TEXT_BASE=0
+CONFIG_FIT=y
+CONFIG_FIT_SIGNATURE=y
tools/Makefile +1 -2
index c93d17a42f..29ff6ed221 100644
@@ -125,7 +125,7 @@ fit_info-objs   := $(dumpimage-mkimage-objs) fit_info.o
 fit_check_sign-objs   := $(dumpimage-mkimage-objs) fit_check_sign.o
 file2include-objs := file2include.o
 
-ifneq ($(CONFIG_MX23)$(CONFIG_MX28),)
+ifneq ($(CONFIG_MX23)$(CONFIG_MX28)$(CONFIG_FIT_SIGNATURE),)
 # Add CONFIG_MXS into host CFLAGS, so we can check whether or not register
 # the mxsimage support within tools/mxsimage.c .
 HOSTCFLAGS_mxsimage.o += -DCONFIG_MXS
--

2.19.2