Searched hist:c8a2a6529dc3ff609281ef4fe5c5bc949c805b5c (Results 1 – 1 of 1) sorted by relevance
| /optee_os/mk/ |
| H A D | checkconf.mk | c8a2a6529dc3ff609281ef4fe5c5bc949c805b5c Thu Jun 06 09:42:46 UTC 2024 Rasmus Villemoes <rasmus.villemoes@prevas.dk> checkconf.mk: do not use full path to generate guard symbol in conf.h
The combination of building with -g3 (which emits definitions of all
defined preprocessor macros to the debug info) and using a full path
to define the name of this preprocessor guard means that the output is
not binary reproducible across different build hosts. For example, in
my Yocto build, the string
__home_ravi_yocto_tmp_glibc_work_stm32mp135fdk_oe_linux_gnueabi_optee_os_stm32mp_3_19_0_stm32mp_r1_1_build_stm32mp135f_dk_include_generated_conf_h_
appears in several build artifacts. Another developer or buildbot
would not build in some /home/ravi/... directory.
In order to increase binary reproducibility, only use the path sans
the $(out-dir)/ prefix of the conf.h file.
Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org>
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
|