mattsm has quit [Quit: Connection closed for inactivity]
sgw has joined #yocto
sgw has quit [Quit: Leaving.]
Vonter has quit [Ping timeout: 248 seconds]
Vonter has joined #yocto
florian has joined #yocto
jmd has joined #yocto
florian has quit [Ping timeout: 252 seconds]
goliath has joined #yocto
rob_w has joined #yocto
DixitP has joined #yocto
<mcfrisk>
has anyone looked into systemd and libfido2 build dependency loop resolutions? feels like either udev would need to be split out of systemd recipe or libfido2 compiled as part of systemd recipe
sgw has joined #yocto
sgw has quit [Client Quit]
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
iokill has quit [Quit: leaving]
iokill has joined #yocto
jmd has quit [Remote host closed the connection]
CrazyGecko has joined #yocto
mckoan|away is now known as mckoan
rfuentess has joined #yocto
Articulus has quit [Quit: Leaving]
DixitP has quit [Quit: Client closed]
frieder has joined #yocto
frieder has quit [Ping timeout: 248 seconds]
ehussain has joined #yocto
mbulut has joined #yocto
frieder has joined #yocto
florian has joined #yocto
ehussain has quit [Remote host closed the connection]
druppy has joined #yocto
<psv>
khem: Ref. LFS in gitsm: if I read the git dock correctly its behaving as instructed in the gitsm.py since it's explisicly told to skip the LFS smudges fetching, and isntead just get pointer files. (GIT_LFS_SKIP_SMUDGE=1 in gitsm line 255)
<psv>
Ref. "inherit useradd on a read only rootfs system in Scarthgap": Is there a way to use nginx, openssl etc. without shadow? Their all inheriting it, and can't be built without. We're using read-only rootf, and poky-tiny.conf which explicitly prohibits shadow (for a good reason.) We also don
<psv>
t have space for it
<psv>
psv: Any help or siggstions highly appreciated :D Struggling with this now for some days..
DixitP has joined #yocto
DixitP has quit [Client Quit]
dexterlb has joined #yocto
<dexterlb>
hello,
<dexterlb>
I have a recipe that sets SRC_URI from a python anonymous function. However, in that case, SRCPV is not automatically generated in time (it is used in the same recipe), since the python function runs after parsing. Is there a way to work around this? I want to choose a different SRC_URI depending on a configuration variable
druppy has quit [Ping timeout: 252 seconds]
frieder has quit [Ping timeout: 246 seconds]
davidinux has quit [Quit: WeeChat 4.3.1]
frieder has joined #yocto
<qschulz>
agodard: can you build a pdf of the docs without warnings right now?
<qschulz>
for me it complains about "a suitable image for latex builder not found"
<qschulz>
(trying inside containers for now, so maybe I just forgot to do something though)
JerryM has joined #yocto
Kubu_work has joined #yocto
Kubu_work has quit [Client Quit]
<JerryM>
kanavin_: `bitbake/bin/bitbake-setup init poky-kirkstone` fails if you don't have a global user/email defined, as I usually want to manually control these this is somewhat of an issue for me
<kanavin_>
JerryM, patches welcome I guess?
<kanavin_>
bitbake-setup does rely on being able to make commits
<JerryM>
kanavin_: so I guess an option to specify the user/email to use for the config repo would be the most appropriate/generic, what do you think?
<agodard>
qschulz: I had issues using the svg2pdfconverter plugin. we shouldn't need it since we already convert images using rsvg-convert. Sometimes after a "clean" the issue disappears too, so I'm not sure what is causing this warning but maybe leftovers from previous builds
<kanavin_>
JerryM, yes, something like that. It could also be in a config file for bitbake-setup itself (I'm going to post a v2 which has support for that).
grma has quit [Remote host closed the connection]
grma has joined #yocto
<JerryM>
kanavin_: alright I'll look forward to those and see what I can do
<JerryM>
should I send potential patches to bitbake-devel?
<kanavin_>
note that you might be expected to rebase and re-test, this is in active development with force pushes
<kanavin_>
I'd suggest you wait for v2 before you send patches
huntercao has joined #yocto
<qschulz>
agodard: indeed, seems like removing the _build directory somehow got rid of that issue
<qschulz>
agodard: FWIW, I think we should also force a version number for pip, maybe even do a pip freeze so that dependencies also are fixed versions?
<qschulz>
for pip packages*
<agodard>
qschulz: yes we could freeze packages installed by pip, although I don't think freezing pip itself is really necessary?
olani has quit [Read error: Connection reset by peer]
<qschulz>
agodard: shouldn't be
olani has joined #yocto
psv has quit [Remote host closed the connection]
halloy4743 has quit [Ping timeout: 252 seconds]
gspbirel56 has joined #yocto
Kubu_work has joined #yocto
Kubu_work has quit [Quit: Leaving.]
rber|res has quit [Read error: Connection reset by peer]
florian has quit [Quit: Ex-Chat]
Guest45 has joined #yocto
huntercao has quit [Ping timeout: 240 seconds]
<Guest45>
Hi guys. I have a question about recommended approach. I have a nxp platform which provides somewhat older Yocto, and bloated with features i don't want. Thus, for example layers are closely coupled, and have long dependency chain of LAYERDEPENDS.
<Guest45>
- Is it more recommended to attempt to extract and copy MACHINE and bsp defs, namely all what is needed, into own slim layers, or
<Guest45>
- just pull N layers and let Yocto resolve this dependency hell, just provide own layer for changes removing features and whatnots from what OEM did
<rburton>
Guest45: depends how little you need from the bsp. copying the bits you want into your own machine isn't a terrible idea. tell nxp that they're making you do this so they hear that from actual customers though.
Tyaku has joined #yocto
<Guest45>
that's not directly from nxp, sorry for the confusion. OEM is using nxp mcu, so this looks like N * oem -> M * nxp & freescale -> ...
<KanjiMonster>
I would think that different platform = different machine; presumably you will have a different u-boot config, dts, etc
<Guest45>
oem's image, distro all is qt rich distro, while i basically need core-minimum-base + some stuff
<rburton>
<cough> that would be slide six or so of my "how to write a bsp" presentation
<Guest45>
yup, that's too
<rburton>
"stop making BSPs that pull in the world"
<Guest45>
:D
<Guest45>
@rburton, can i plz has the link to such pdf? :)
<Tyaku>
Hello, Up to now, we was creating images for a unique MACHINE and we was doing the board distinction at runtime (using variables from DTS). But now we have to create multiple machines because there are things that needs to change at compile time. I would like to know if it's possible to do something like this: DEPENDS:append:(machinea:machineb) = "", instead of DEPENDS:append:machinea = "" and
<Tyaku>
DEPENDS:append:machineb = "" ? I mean: Is it possible to do a "or"
<Tyaku>
Reformulation: If I want to append in DEPENDS the same thing for one of N machines, is it possible ? or we need to copy the line for each machines ?
<Tyaku>
Reformulation (again..): The idea is to append something to a variable for any machines within a list.
<Guest45>
Tyaku - i'm no expert, but i think it should be possible - for example might be fragments to include different DTS?
<Guest45>
yup, found it thanks @rburton - will dig into this
<rburton>
Tyaku: if there something that ties the machines together then you can create a new machineoveride, like how the qemu machines in core create a new qemuall override that can be used to override for "all qemu machines"
cyxae has joined #yocto
cyxae has quit [Client Quit]
cyxae has joined #yocto
<Tyaku>
Thanks rburton, I am watching MACHINEOVERRIDES and I'm going to check how qemu use the machines in yocto.
<qschulz>
but i see we already have some code-block formatting consistency issues
<qschulz>
not that it is a blocker for that plugin
PhoenixMage has joined #yocto
davidinux has quit [Quit: WeeChat 4.3.1]
druppy has quit [Ping timeout: 252 seconds]
mckoan is now known as mckoan|away
leon-anavi has joined #yocto
JerryM has quit [Quit: Konversation terminated!]
goliath has joined #yocto
florian has joined #yocto
druppy has joined #yocto
pidge has joined #yocto
jmd has joined #yocto
pidge has quit [Read error: Connection reset by peer]
pidge has joined #yocto
Daanct12 is now known as Danct12
rfuentess has quit [Remote host closed the connection]
<khem>
psv:do you ahve read-only-rootfs in IMAGE_FEATURES ? if you do then it should drop depenendency on shadow globally
mbulut_ has joined #yocto
salahaldeen___ has joined #yocto
OnkelUll_ has joined #yocto
deribaucourt has joined #yocto
yocti` has joined #yocto
yocti has quit [Killed (NickServ (GHOST command used by yocti`))]
woky- has joined #yocto
Emantor_ has joined #yocto
yocti` is now known as yocti
philipl__ has joined #yocto
yocton_ has joined #yocto
|Xagen has joined #yocto
dvergata1 has joined #yocto
drkhsh_ has joined #yocto
druppy has quit [Ping timeout: 272 seconds]
mbulut has quit [*.net *.split]
Emantor has quit [*.net *.split]
Xagen has quit [*.net *.split]
Dvergatal has quit [*.net *.split]
ederibaucourt has quit [*.net *.split]
OnkelUlla has quit [*.net *.split]
Saur has quit [*.net *.split]
philipl_ has quit [*.net *.split]
salahaldeen has quit [*.net *.split]
zwelch has quit [*.net *.split]
woky has quit [*.net *.split]
yocton has quit [*.net *.split]
drkhsh has quit [*.net *.split]
salahaldeen___ is now known as salahaldeen
Emantor_ is now known as Emantor
zwelch has joined #yocto
Saur has joined #yocto
yocton_ is now known as yocton
geoff_ has joined #yocto
geoffhp has quit [Ping timeout: 248 seconds]
geoff_ is now known as geoffhp
Austriker has joined #yocto
<Austriker>
Hi, I am trying to integrate Mender A/B OTA with an x86 build based on meta-amd Milan machines. The build of the default amd-distro with milan works like a charm but when I add mender I get a circular import error `ERROR: Task /workspaces/yocto-distros/build/../meta-distro/recipes-images/images/ap-image.bb:do_bootimg has circular dependency on
<Austriker>
'/workspaces/yocto-distros/build/tmp-glibc/deploy/images/ap-milan//workspaces/yocto-distros/build/tmp-glibc/work/swan_ap_milan-oe-linux/ap-image/1.0/ap-image-1.0/efi_img/EFI/BOOT/*': No such file or directory`. What is the best way to debug this kind of issues without pulling out pieces of code that are actually usefull ?
vvn has joined #yocto
dankm has quit [Remote host closed the connection]
Vonter has quit [Ping timeout: 244 seconds]
dankm has joined #yocto
Austriker has quit [Quit: Client closed]
mbulut_ has quit [Ping timeout: 245 seconds]
leon-anavi has quit [Remote host closed the connection]