seninha has quit [Read error: Connection reset by peer]
Wouter0100 has quit [Ping timeout: 258 seconds]
sakoman has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Wouter0100 has joined #yocto
camus has quit [Ping timeout: 248 seconds]
RobertBerger has joined #yocto
rber|res has quit [Ping timeout: 246 seconds]
mckoan|away has quit [Ping timeout: 276 seconds]
camus has joined #yocto
florian__ has quit [Ping timeout: 276 seconds]
mckoan|away has joined #yocto
better_sleeping[ has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
better_sleeping[ has left #yocto [#yocto]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
angolini has quit [Quit: Connection closed for inactivity]
angolini_ has quit [Quit: Connection closed for inactivity]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
Lihis has quit [Quit: Quitting]
Lihis has joined #yocto
kroon has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
goliath has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
tre has joined #yocto
goliath has quit [Quit: SIGSEGV]
frieder has joined #yocto
RobertBerger has quit [Quit: Leaving]
michalkotyla has joined #yocto
frieder has quit [Ping timeout: 240 seconds]
goliath has joined #yocto
frieder has joined #yocto
frieder has quit [Ping timeout: 246 seconds]
gsalazar has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
frieder has joined #yocto
michalkotyla has quit [Quit: michalkotyla]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
frieder has quit [Ping timeout: 246 seconds]
xmn_ has quit [Ping timeout: 246 seconds]
Schlumpf has joined #yocto
frieder has joined #yocto
GuestNew118 has joined #yocto
<GuestNew118>
Hello guys I'm searching the best way to avoid file installation from recipe. I would like to remove sysV init script but I want to keep the binary inside the rootfs. Any suggestion ? Thx.
wkawka has joined #yocto
<wkawka>
Hi, did you encountered a warning: linker input file unused because linking not done and then error: linker input file not found: No such file or directory? I was looking for info or solution but I couldn't find anything that is related when I'm using Golang, not C. This error occures during build when Makefile is used
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
oneronc has joined #yocto
<oneronc>
ין
<oneronc>
*hi
<oneronc>
when I want to add extra features to this recipe:
<qschulz>
that should give you the whole history of the variable for thgis recipe
<qschulz>
then you can try to figure out if something's messing with your variable in some other file
<qschulz>
likely a PACKAGECONFIG_remove somewhere
<qschulz>
or maybe your PACKAGECONFIG_append_pn-strongswan isn't taken into account
<oneronc>
why wouldnt it be taken into account ?
Juanosorio94 has joined #yocto
<Juanosorio94>
Hey guys! Which target do I build when I want to use my modules and all other functionality?
<Juanosorio94>
I had build core-image-minimal just to test my kernel, but that doesnt include my modules per se
<qschulz>
oneronc: because your file might not be parsed?
<qschulz>
I don't know
<qschulz>
that's part of the debugging process :)
<qschulz>
first check the history of the variable
<qschulz>
Juanosorio94: you need to include the modules explicitly
<qschulz>
Juanosorio94: add kernel-modules (for all modules) in your image
<Juanosorio94>
qschulz: how do I do that?
<Juanosorio94>
I have inherit module in my recipe file, the layer is already included and its built. During compile I added an install step
<Juanosorio94>
no nvm I have do_install
florian__ has joined #yocto
<qschulz>
Juanosorio94: is it an out-of-tree kernel module or one from the Linux tree?
<Juanosorio94>
out of tree
<qschulz>
ah ok
<qschulz>
oe-pkgdata-util list-pkgs <your-recipe>
<qschulz>
will output the name of the packages created by your recipe
<qschulz>
it'll very likely be named "kernel-module-xxxxx"
<qschulz>
then you need to add this package to your image via an addition to IMAGE_INSTALL/CORE_IMAGE_EXTRA_INSTALL in your image recipe or maybe use MACHINE_EXTRA_RDEPENDS in your machine configuration file (if core-image-minimal actually uses this variable, I'm not entirely sure)
wkawka has quit [Quit: Client closed]
<oneronc>
I created a file called strongswan_%.bbappend with this content:
<oneronc>
how can I tell what parameters it passed to the configure script ?
<oneronc>
for some reason it wont install the command line tools
nemik has joined #yocto
michalkotyla has joined #yocto
jclsn has joined #yocto
jclsn has quit [Client Quit]
<michalkotyla>
Hi, is there any option to check why my image requires some package? I know about "bitbake -g image", but it only confirms that the package "do_populate_lic" task is actually required by image, but I still do not know why. I do not see any area of code which can have an impact on that.
GuestNew118 has quit [Quit: Client closed]
<ptsneves>
hey, what triggers the yocto project auto builder?
denisoft81 has joined #yocto
zoologist has left #yocto [WeeChat 2.8]
oneronc has quit [Quit: Client closed]
florian has joined #yocto
Schlumpf has quit [Quit: Client closed]
m4ho has quit [Ping timeout: 244 seconds]
twnqx has joined #yocto
GNUmoon has quit [Remote host closed the connection]
ptsneves has quit [Quit: Client closed]
m4ho has joined #yocto
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #yocto
wkawka has quit [Quit: Client closed]
GNUmoon has joined #yocto
thomasd13 has joined #yocto
Juanosorio94 has quit [Quit: Client closed]
fennec has joined #yocto
ptsneves has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<fennec>
Hi everyone.
<fennec>
I'm trying to build a tauri app in a yocto-xwayland distro
<fennec>
for that I need to enable the x11 backend of gtk
<fennec>
but when I remove wayland from gtk's PACKAGE_CONFIG, I get a 'GDK backend not configured' (or smth similar)
<fennec>
I've been looking at the docs but fail to see how to do it
<fennec>
also searching on internet is not helping me anymore, it's been a while already and I keep finding the same pages
Schlumpf has joined #yocto
wkawka has joined #yocto
<rburton>
fennec: why are you removing wayland?
<rburton>
gtk can build both x11 and wayland support
leon-anavi has joined #yocto
<fennec>
well I was deseperrate to build gtk with x11 enabled
<fennec>
it's really annoying things like xserver-xorg for instance build well
<fennec>
but I can't get gtk to enable the x11 backend
<fennec>
which is needed by tauri
<fennec>
since it has a dependency on gdk-x11
<rburton>
just ensure your DISTRO_FEATURES have x11, and it will enable it
<rburton>
unless your distro forces it off, of course
<paowz_>
Hello there ! A question regarding systemd. With Dunfell, enabling a service from a recipe with SYSTEMD_AUTO_ENABLE would cause the creation of a symlink from /lib/systemd/system to /etc/systemd/system/blabla for the given service.. With Honister, for some reason, this symlink is not created.. Am I missing something ? Thanks :-)
<fennec>
yeah I tried the DISTOR_FEATURE trick already
<fennec>
What can I do if the distro forcesit offN
<rburton>
fennec: bitbake gtk+3 -e |less and search for DISTRO_FEATURES=. check that it contains x11, and if it doesn't the lines above will tell you what it evaluated.
<paowz_>
.. or REQUIRED_DISTRO_FEATURES = "x11" ??
<rburton>
fennec: if that does contain x11 then also check the PACKAGECONFIG= assignment. the default value contains x11 if DISTRO_FEATURES contains x11
<rburton>
paowz_: that is entirely unrelated
<paowz_>
rburton: ok.. at least, I tried..
<fennec>
ok thanks trying it rn
<rburton>
paowz_: suggestions are best if they're useful. if you don't understand what a variable is for, probably best to not suggest other waste time trying pointless changes
<paowz_>
ok, and regarding my question, what would you suggest ?
<fennec>
ok so it took me a while but I can see x11 in the DISTRO_FEATURES
<GuestNew>
Hello, I would like to create 2 images (client/prod) based on the same platform but with different packages. So where is the best way to configure package's SRC_URI/REV ? I'm thinking about Ditros but I'm not sure that is the best method... any advice ?
<rburton>
fennec: whats the actual value of PACKAGECONFIG?
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
<fennec>
PACKAGECONFIG="opengl wayland glx"
<fennec>
rn gtk seems to be finding the x11 backend
<fennec>
I should check for the .pc file tho
GNUmoon has quit [Remote host closed the connection]
<fennec>
my current problem is wpebackend-fdo does not build
<fennec>
| /mnt/code/performance-1-os-yocto/build/tmp/work/aarch64-mx8mp-tdx-linux/wpebackend-fdo/1.4.1-r0/wpebackend-fdo-1.4.1/src/ws.cpp:30:10: fatal error: EGL/eglmesaext.h: No such file or directory
<fennec>
| 30 | #include <EGL/eglmesaext.h>
<fennec>
| | ^~~~~~~~~~~~~~~~~~
<fennec>
| compilation terminated.
seninha has joined #yocto
<fennec>
ok this is fixed by using the recipe from meta-webkit
<rburton>
PACKAGECONFIG="opengl wayland glx"
<rburton>
^ no x11
<fennec>
oh wait I missed it?
<rburton>
look above the assignment in the -e output and you'll see the default should include x11 but I expect either a bbappend or packageconfig:remove is deleting it
<qschulz>
GuestNew: proper way is to have a new distro with two different recipes (different version in the bb filename and then use PREFERRED_PROVIDER_recipe = "version-you-want"
nemik has quit [Ping timeout: 276 seconds]
<GuestNew>
qschulz thank you for reply :)
GNUmoon has joined #yocto
<qschulz>
GuestNew: if your package is not used by any other package (RDEPENDS) or your recipe by any other recipe (DEPENDS), you could also just duplicate the recipe and rename it slightly differently
<qschulz>
e.g. recipe-prod instead of recipe
<qschulz>
and then in the image for prod, instead of adding "package" you add "package-prod"
<qschulz>
something along those lines
<qschulz>
not best practice, error-prone but much more efficient
<qschulz>
ptsneves: you'll need to send a v4 with the Upstream-Status changed from Inappropriate to Submitted + the link to the pull request BTW
<GuestNew>
qschulz I have taken due note of this :)
nemik has joined #yocto
<ptsneves>
qschulz ah ok will do
<RP>
ptsneves: looking at the queues in poky-contrib, I suspect not
<ptsneves>
then i probably will need to wait if it is approved or not :( this requirement on the upstreaming to python was a bit of a bummer
<ptsneves>
ok
Thorn has joined #yocto
GNUmoon has quit [Remote host closed the connection]
<fennec>
rburton: What is the way around then?
<qschulz>
ptsneves: we've been fighting a lot to reduce the number of patches we maintain over time, so it is more difficult than in the past to contribute patches which aren't contributed to their upstream project
<qschulz>
it's a bit more time consuming for contributors, but a lot less pain for maintainers
<ptsneves>
qschulz fair enough. Thanks for the explanation.
<rburton>
fennec: first find out why the default PACKAGECONFIG, which sets x11 if x11 is in DISTRO_FEATURES, isn't being respected. that's in the bit above the assignment in the -e output
<rburton>
fennec: pastebin that block if you want a hand
<fennec>
will do thanks a lot
<fennec>
ok so I change DISTRO_FEATURE:append to DISTRO_FEATURES += " x11"
<fennec>
and it seems to do the trick
<fennec>
but I may have a bigger problem
<fennec>
ERROR: Nothing PROVIDES 'virtual/egl' (but /mnt/code/performance-1-os-yocto/build/../layers/openembedded-core/meta/recipes-gnome/gtk+/gtk+3_3.24.14.bb DEPENDS on or otherwise requires it)
<fennec>
imx-gpu-viv PROVIDES virtual/egl but was skipped: incompatible with machine verdin-imx8mp (not in COMPATIBLE_MACHINE)
<fennec>
imx-gpu-viv PROVIDES virtual/egl but was skipped: missing required distro feature 'wayland' (not in DISTRO_FEATURES)
<fennec>
imx-gpu-viv PROVIDES virtual/egl but was skipped: incompatible with machine verdin-imx8mp (not in COMPATIBLE_MACHINE)
<fennec>
imx-gpu-viv PROVIDES virtual/egl but was skipped: missing required distro feature 'wayland' (not in DISTRO_FEATURES)
<fennec>
ERROR: Required build target 'gtk+3' has no buildable providers.
<fennec>
Missing or unbuildable dependency chain was: ['gtk+3', 'virtual/egl']
<rburton>
your append was most likely missing a ' '
<rburton>
:append = " x11"
<rburton>
+= is more likely to be a problem, append would always work
<rburton>
(might be easiest if you just pastebin the entire -e output)
<rburton>
+= on DISTRO_FEATURES doesn't work if your distro uses ?= to assign
GNUmoon has joined #yocto
<fennec>
well += made a diff, with append I get the same PACKAGE_CONFIG as before
<otavio>
fennec: it does as x11 is not "supported" by the gpu stack anymore
<fennec>
oh does that mean I can't get use smth that depends on x11? otavio:
<thomasd13>
Hi, I've got a piece of software, which I would like to write a recipe for it. Problem is, the software is built with cmake-configuration. That cmake-configuration requires a cmake-toolchain-file at a specific absolute path (/var/foo).
<thomasd13>
Can I somehow "mock" this /var/foo path with yocto?
<thomasd13>
Like the package is build within an container, which I can do whatever I would like
GuestNew has quit [Quit: Client closed]
GuestNew has joined #yocto
lukma_ has quit [Quit: Lost terminal]
<rburton>
thomasd13: not trivially
<rburton>
what if you wanted to build that outside of a container as a non-root user?
<rburton>
sounds like you *have* to build in their own build container, which is madness
<thomasd13>
rburton, okay - so there is no tool which "emulates" a whole small linux system like docker? I thought maybe fakeroot is something which I can work with. But I think it isn't :)
kscherer has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<thomasd13>
Another question: package-a builds (but doesn't deploy) static libraries. package-b must link with libraries which are built from package-a. How looks like the relative path from package-b to package-a at build time?
<thomasd13>
Assuming I specify package-b DEPENDS on package-a
<GuestNew>
Hi, is it possible for a recipe to inherit from an other .bb ? the purpose is to create 2 recipes based on the same one "as template". The main recipe is given by the vendor BSP and i would like to keep it without modification
<RP>
thomasd13: you can emulate a system with qemu or use a container but there are speed and permissions challenges in most cases
<ptsneves>
GuestNew no. What you want is to use an .inc file with the common parts and require it in each .bb
<ptsneves>
or what you want is a bbappend. That just applies your modifications on top and you remain with the vendor's recipe
<qschulz>
GuestNew: yes you can, but you should follow what ptsneves said about .inc
<RP>
thomasd13: depending on another recipes build directories is fraught with danger, you usually add something to install into the sysroots to allow them to share data
<ptsneves>
qschulz oh dang. Saying it is possible....it is but should be "forbidden"
<ptsneves>
:)
<GuestNew>
ptsneves qschulz Thanks a lot for the support:) I will definitively use the .inc based on ditros.
<qschulz>
thomasd13: if you installed the static libs properly in a SYSROOT_DIRS, it shgould be available in recipe-b in its recipe-sysroot directory
<qschulz>
that's the only way this should be done, you shouldn't traverse the TMPDIR to find the source/build directory of recipe-a
<thomasd13>
RP, normally I would totally agree with you. But in this special case... package-A is a huge blob of software, which produces ~500 libs for whatever, and projects which rely on that libs just picking 2-3 of them which they really need
<thomasd13>
So I would like to avoid to deploy 497 static libs on that system which are not used
Thorn has joined #yocto
<thomasd13>
ahh but wait - qschulz the libs just appear in the recipe-sysroot right? Not at the targetfs
<ptsneves>
thomasd13 yes and you can gate your recipe to only stage the few libs you want
<thomasd13>
Ahhh, got it! Thanks guys!
Schlumpf has joined #yocto
camus has quit [Quit: camus]
<qschulz>
thomasd13: files will always be in a package if they are meant to be used in other recipe sysroots (because the files need top be installer to be accessible from other recipes, and yany installed file needs to be in a package otherwise you get a warning/error), but it's up to you to install the package or not
<thomasd13>
thank you qschulz !
prabhakarlad has joined #yocto
amitk has quit [Quit: leaving]
amitk has joined #yocto
Wouter0100 has quit [Read error: Connection reset by peer]
Wouter0100 has joined #yocto
<fennec>
otavio: does that mean I can't use x11?
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
manuel has joined #yocto
<manuel>
Hi all
<manuel>
Is there a rule of thumb wether to put inherits at the top or at the bottom of a recipe?
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
tre has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
kroon has quit [Quit: Leaving]
thomasd13 has quit [Ping timeout: 246 seconds]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
sakoman has joined #yocto
OnkelUll_ is now known as OnkelUlla
nemik has quit [Ping timeout: 246 seconds]
<ptsneves>
manuel normally at the end as it is a glorified require AFAIK, and that means that where it is included affects the parsing order. Either that or I have been seeing pixies, meaning: i can be wrong
<ptsneves>
sorry normally at the beggining, the inherit is usually at the begging
<manuel>
ptsneves: Thanks
nemik has joined #yocto
<wyre>
hi guys, I'm not sure when I modify my DT as this https://bpa.st/HQAA the do_patch task for the linux kernel Makefile fails ...
<wyre>
I'm just actually adding my dts to the Makefile ... I'm guessing this shouldn't depend on specific changes in the DTS itself, am I right?
<wyre>
I mean ... if those changes would be causing this error ... the error should happen in do_compile task, right?
<wyre>
but not sure when I revert the changes ... the image is properly built 🤔
<wyre>
but it patches the Makefile, not the dts itself ... so ... not sure what's happening
m4ho has quit [Ping timeout: 248 seconds]
amitk has quit [Quit: Lost terminal]
<wyre>
may this be due the dts is wrong ... any dtb is produced/built so the do_patch task fails?
amitk has joined #yocto
<wyre>
I find this so weird, the Makefile patch task shouldn't depend on whether dtb is produced or not ...
<zeddii>
wyre: do patch runs long before anything is built, so anytthing in the build, wouldn't be causing do_patch to fail.
<wyre>
zeddii, then ... not sure why when I modify my dts ... this do_patch task fails ...
<zeddii>
if it is the patch you linked to before, the path to the file is completely wrong. you are patching something in the source tree, not in your layer. I'd suggest hunting around for other layers with kernel recipes and patches, and you'll see the type of path they use (git/Makefile, as an example)
<wyre>
zeddii, you mean I should have the kernel source tree in my layer?
amitk has quit [Ping timeout: 260 seconds]
amitk_ has joined #yocto
<wyre>
zeddii, with my first custom dts the patch was working 🤔
<wyre>
zeddii, I wouldn't like to include the whole kernel source tree in my layer, just to add a custom dts to the current kernel I'm using
xmn has joined #yocto
m4ho has joined #yocto
<zeddii>
no. the kernel patches like anything else. look at any patch, to any package.
<zeddii>
let me look at what you linked again. I only scanned it.
<zeddii>
so that's a diff of a patch in the layer, so yes, that's ok. if it is failing to patch, then it could just be that the context is wrong, or something else. What was the actual do_patch error again ?
<wyre>
zeddii, you mean the whole log.do_patch?
<zeddii>
or just the error that the build throws, should be enough.
gchamp has quit [Remote host closed the connection]
<wyre>
wow ... now apparently it's working 🤔.... it reaches the do_compile task at least ...
<wyre>
let me reproduce it ... I think this happens after I do a bitbake -c clean <image> and `rm -rf tmp`
GuestNew has quit [Quit: Client closed]
qschulz has quit [Ping timeout: 240 seconds]
goliath has quit [Quit: SIGSEGV]
kscherer has quit [Quit: Konversation terminated!]
Schlumpf has quit [Quit: Client closed]
ykrons has quit [Quit: Ex-Chat]
selff has joined #yocto
<selff>
hello everyone. I'm trying to edit the "/etc/hostname" file during boot.
<selff>
name of hostname is created by the "base-files" recipe when building image. it like this:
<selff>
but instead i want to write the content of "Serial" number in "/proc/cpuinfo" while the device is booting. how can i do that? i wrote a script for this, but i have a problem on how to do it.
<prabhakarlad>
Hi all, previously distutils_do_install was used to install the pyhton package, but with the update to yocto Im getting error: distutils_do_install: not found. Any pointers how I can get around this?
<rburton>
there was a session at the Yocto Summit a couple of weeks ago which covered this. It will be on youtube at some point, but this is a good reason why it's wise to go :)
<rburton>
tlwoerner: any eta on the summit presentations being on youtube?
<wyre>
zeddii, not sure why the second time (without any change) worked but not the first one https://bpa.st/SFGQ
prabhakarlad has quit [Quit: Client closed]
alefir_ has joined #yocto
alefir has quit [Ping timeout: 240 seconds]
<ndec>
tlwoerner: rburton : done.. sorry about that. I think the title was truncated.. it allows 100 char only, and I didn't notice. Fixed now.
<tlwoerner>
ndec: also, apparently the videos don't show up in the "videos" tab?
<tlwoerner>
ndec: only in the "playlists" tab
alimon has quit [Remote host closed the connection]
<ndec>
hmm.
<ndec>
right.. they are 'unlisted'.. will fix that too
denisoft81 has quit [Remote host closed the connection]
<otavio>
fennec: with mainline you can; nxp bsp not anymore
denisoft81 has joined #yocto
<ndec>
tlwoerner: fixed!
denisoft81 has quit [Client Quit]
selff has quit [Quit: Client closed]
denisoft81 has joined #yocto
selff has joined #yocto
<rburton>
ndec: awesome thanks
mckoan|away has quit [Ping timeout: 246 seconds]
mckoan|away has joined #yocto
Thorn has quit [Ping timeout: 260 seconds]
v0n has joined #yocto
selff has quit [Ping timeout: 252 seconds]
<fennec>
otavio: thanks for the clarification
alimon has joined #yocto
gsalazar has quit [Ping timeout: 248 seconds]
Juanosorio94 has joined #yocto
<fennec>
So the chip I'm using is a NXP i.MX8M Plus
<fennec>
Does it mean I can't use something that depends on x11?
<otavio>
fennec: you can use xwayland
<rburton>
not if you can't build an app that needs gtk with x11 you can't
<fennec>
the distro is tdx-xwayland
<fennec>
thing is I need to run tauri
<fennec>
a rust library that depends on gdk-x11-sys
<fennec>
rburton: unsure what what you say that implies in my case
<otavio>
fennec: so tauri needs fixing ;-)
<otavio>
it shouldn't have a hard depends on x11
goliath has joined #yocto
<fennec>
tauri needs a lot of love atm
<fennec>
I'll tell them tho
<yudjinn[m]>
hello, Im running into an issue where yocto is looking for python sit-packages in `${STAGING_DIR_NATIVE}/usr/include/python3.5m` Im confused why the m is there in the first place. Im using `inherit python3native` and `depends python3-native python3-numoy-native`
ptsneves has quit [Ping timeout: 252 seconds]
Juanosorio94 has quit [Quit: Client closed]
wkawka has quit [Quit: Client closed]
florian has quit [Quit: Ex-Chat]
florian__ has quit [Ping timeout: 276 seconds]
prabhakarlad has joined #yocto
kscherer has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 276 seconds]
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
kranzo has joined #yocto
<kranzo>
hi there,
<kranzo>
is there a way of extending the PATH variable created by the esdk?
armhzjz has joined #yocto
<armhzjz>
Trying to build an image for a Raspberrypi 3B. Getting this message saying that LIC_FILES_CHKSUMpoints to an invalid file (i.e. LICENSE) which in deed does not exist. Does anybody know how to go over this, if the meta-layer repository does not provide this license in the expected directory? The meta-layer in question is meta-raspberrypi, and I created a bbappend to include SRC_URIto the firmaware-nonfree
<armhzjz>
repository, branch bullseye.
florian__ has joined #yocto
<rburton>
your bbappend probably broke it. can you pastebin it?
<rburton>
so your append changes the src_uri, so you need to fix the license references
<armhzjz>
haaa ... damn....yeah of course. The thing is, I am moving all my stuff from gatesgarth to kirkstone and I am doing a mess here.... silly mistake. Thank you very much man!
<yudjinn[m]>
how can I write a patch without using git?
armhzjz has quit [Quit: leaving]
peoliye has joined #yocto
kranzo has quit [Quit: Client closed]
qschulz has joined #yocto
fennec has quit [Quit: WeeChat 3.5]
<zyga[m]>
@yudjinn[m]:libera.chat: you can use diff perhaps
twnqx has quit [Ping timeout: 276 seconds]
<yudjinn[m]>
tried, it doesnt really like it
<zyga[m]>
I mean, make two directory trees, one with the original, modify the second one and diff the files
fennec has joined #yocto
<fennec>
I'm searching a way to share files within recipes. Is that using class? I can't seem to find the relevant doc
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<rburton>
a class is one way, or just a .inc file you require in each recipe
<fennec>
will .inc work for git repos?
otavio has quit [Ping timeout: 248 seconds]
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
otavio has joined #yocto
denisoft81 has quit [Quit: Leaving]
vladest has quit [Quit: vladest]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
vladest has joined #yocto
kranzo has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
seninha has quit [Quit: Leaving]
seninha has joined #yocto
kranzo has quit [Quit: Client closed]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
leon-anavi has quit [Quit: Leaving]
jpuhlman has quit [Ping timeout: 256 seconds]
peoliye has quit [Quit: Client closed]
sakoman has quit [Quit: Leaving.]
diamondman has joined #yocto
<diamondman>
Hello everyone. I created a recipe to hold .proto files so the multiple consuming recipes can pull the proto files directly into their sysroot. I made this 'company-protos' recipe `inherit allarch` because it does not produce any platform/architecture specific files. Several class-target recipes were then made to depend on this protos recipe, and that worked well.
<diamondman>
There are also some class-native recipes that need the proto files, and most of them are `BBCLASSEXTEND = "native"`. I added `DEPENDS += "company-protos"` which works for the class-target build, but when built in class-native mode, bitbake looks for `company-protos-native` which does not exist (because the protos recipe is allarch).
<diamondman>
Any advice would be greatly appreciated, thank you in advance.
<diamondman>
I understand that bitbake will append `-native` to dependencies under certain circumstances, but I don't know all those cases yet, and I do not know how to prevent bitbake from automatically adding -native to a dependency that is allarch.
kscherer has quit [Quit: Konversation terminated!]