diff options
author | Alper Ak <alperyasinak1@gmail.com> | 2025-06-23 15:56:08 +0300 |
---|---|---|
committer | Khem Raj <raj.khem@gmail.com> | 2025-06-26 07:26:19 -0700 |
commit | 9650061e408de7c9d8619c3915732ce0e3e1074c (patch) | |
tree | f26b1b52bddcce7b61c97a5a2773b20b6d4da842 /meta-python/recipes-devtools/python/python3-inotify/new-test-inotify.patch | |
parent | 2f941edce174ee1063f2c28821b81976bd6989de (diff) | |
download | meta-openembedded-9650061e408de7c9d8619c3915732ce0e3e1074c.tar.gz |
wifi-test-suite: Fix compile issue
- Variables such as CC, CXX and related variables are usually assigned in core class like gcc.bbclass. For example, CC is assigned this specific value:
CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}"
If you use the += operator to add flags to the CC variable early in your recipe, your changes will be overwritten and lost because BitBake applies class assignments to CC at a later stage, which replaces any previous modifications.
We should use :append operation to ensures that additions are applied to the final value, after all assignments from core classes have been processed. As a result, when you want to extend variables that may be set in core classes (like CC in gcc.bbclass), you should use the :append syntax to guarantee your changes are preserved in the final build environment.
- Using CFLAGS is the standard way to pass compiler flag for C projects.
- The Makefile of the project doesn't respect to append to CFLAGS so added 0006-make-CFLAGS-appendable.patch to make CFLAGS appendable.
Signed-off-by: Alper Ak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-inotify/new-test-inotify.patch')
0 files changed, 0 insertions, 0 deletions