Skip to content

fix: local.conf is overwritten on script invocation#11

Open
abinjose-qualcomm wants to merge 1 commit intoqualcomm-linux:mainfrom
abinjose-qualcomm:fix-conf-overwrite
Open

fix: local.conf is overwritten on script invocation#11
abinjose-qualcomm wants to merge 1 commit intoqualcomm-linux:mainfrom
abinjose-qualcomm:fix-conf-overwrite

Conversation

@abinjose-qualcomm
Copy link
Contributor

Users expect local.conf to remain unchanged after it is created, as this file is intended for their own custom modifications. To support this behavior, the configuration generated from the kas configuration files can be written to auto.conf instead of local.conf.

Fixes #8

cp "$KAS_BUILD_DIR/conf/bblayers.conf" build/conf/bblayers.conf

# create local.conf to avoid auto-generated file from oe-init-build-env
# existing local.conf file shouldn't be affected

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the issue with the auto-generated one from oe-init-build-env?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The order of operations follows auto.conf first, then local.conf. The auto-generated local.conf from oe-init-build-env sets a default machine value which would overwrite the machine set in auto.conf.

In the absence of this step, we would get this behavior:

abinjose@hu-abinjose-hyd:/local/mnt/workspace/projects/software-images/ws-repo/build$ cat conf/local.conf | grep ^MACHINE
MACHINE ??= "qemux86-64"
abinjose@hu-abinjose-hyd:/local/mnt/workspace/projects/software-images/ws-repo/build$ bitbake -e | grep ^MACHINE=
MACHINE="qemux86-64"
abinjose@hu-abinjose-hyd:/local/mnt/workspace/projects/software-images/ws-repo/build$ rm conf/local.conf
abinjose@hu-abinjose-hyd:/local/mnt/workspace/projects/software-images/ws-repo/build$ bitbake -e | grep ^MACHINE=
MACHINE="qcs9100-ride-sx"

I'll update the comments in the script.

Users expect local.conf to remain unchanged after it is created,
as this file is intended for their own custom modifications. To
support this behavior, the configuration generated from the kas
configuration files can be written to auto.conf instead of local.conf.

Signed-off-by: Abin Joseph <abinjose@qti.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

local.conf gets replaced at every setup-environment call

2 participants