[yocto] #yocto #dunfell Console Standard input dirty without "tools-sdk" image feature

2021-08-24 Thread ivin.lim via lists.yoctoproject.org
Using dunfell 3.1.8

Will post this inquiry while doing my own investigation. When outputting to the 
debug console that involves standard input(ex. busctl, systemctl status), the 
output seems misaligned and dirty.
But I noticed this can be easily fixed by adding to the "tools-sdk" to the 
EXTRA_IMAGE_FEATURES.
I'm curious to know what else tools-sdk seems to besides adding development 
tools(ex. gcc,make)

Below is the snapshot when tools-sdk isn't included in the image built

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54548): https://lists.yoctoproject.org/g/yocto/message/54548
Mute This Topic: https://lists.yoctoproject.org/mt/85105833/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #dunfell:https://lists.yoctoproject.org/g/yocto/mutehashtag/dunfell
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] #yocto Preferred development workflow

2021-07-12 Thread ivin.lim via lists.yoctoproject.org
sorry about that, right now the config files are placed in the files directory 
of the recipe which builds the module.

Sample snippets of the recipe concerning this config file, I removed the rest 
of lines.
SRC_URI = " \
file://config.json \
"

do_install_append() {
install -m 0644 ${WORKDIR}/config.json ${D}/etc/directory/
}

If I were to have the config files placed on a separate recipe, would that mean 
making multiple of these recipes depending on the number of projects?
I did thought also of adding it in the image recipe but probably this wouldn't 
look well if more things get added.

Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54107): https://lists.yoctoproject.org/g/yocto/message/54107
Mute This Topic: https://lists.yoctoproject.org/mt/84171384/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] #yocto Preferred development workflow

2021-07-12 Thread ivin.lim via lists.yoctoproject.org
Hi everyone,

I'm curious on a good approach when dealing with multiple projects

I've just started out  yocto and have already  created our own meta-layer which 
contains our modules. Now these modules would sometimes have config files and 
this could vary when each project that we have would use these recipes. I'm 
thinking of a way to control this. And I don't think having one branch per 
project is a good style. Right now the best way I can think of is creating 
seperate "project layers" (ex. meta-project1, meta-project2) and from there 
create those .bbappends which would point to the project-specific conf files.

But I was wondering if there is a better way of handling it. Thanks.

Cheers.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54105): https://lists.yoctoproject.org/g/yocto/message/54105
Mute This Topic: https://lists.yoctoproject.org/mt/84171384/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-