<jclsn[m]>
I also don't understand what he means by the find command. Just search for the file?
GillesM has joined #yocto
dtometzki has joined #yocto
troth has quit [Ping timeout: 246 seconds]
GillesM has quit [Quit: Leaving]
<RP>
jclsn[m]: can you share the recipe you tried? The idea should work
<jclsn[m]>
RP: I think the problem was that the dot.profile file is only loaded for non-root users
<jclsn[m]>
I appended to the /etc/profile directly now
<jclsn[m]>
And I can now confirm that it worked
<jclsn[m]>
s/dot.//etc/skel/./, s/file//
<jclsn[m]>
Now only this annyoing eglfs issue is missing..
<jclsn[m]>
But no one here seems to actually work with a Raspberry Pi :P
<RP>
jclsn[m]: no idea on that I'm afraid
<jclsn[m]>
RP: Thanks anyhow
<jclsn[m]>
Unfortunately almost no one is here on the weekends
<jclsn[m]>
I am working on this personal arts projects where I want to bundle a simple Qt applications with a minimal Linux on an SD card and I thought doing it in Yocto would be good training exercise. Seems like it is more complicated than I though
<jclsn[m]>
Everything works on Raspbian, but it is annyoing to reinstall and configure it every time
sakoman has joined #yocto
<RP>
jclsn[m]: a lot of the people working on the project do it as a job now which means they want to escape on weekends. It has changed over the years...
* RP
isn't sure why he is here
<yolo>
is there a command like: bitbake core-image-minimal download --- to just download all pkgs without building them
<yolo>
want to compare build time on two machines
<yolo>
ok, so it's: bitbake <target> --runall=fetch
xmn has joined #yocto
<jclsn[m]>
yolo: You could just build it once and then delete the build folder and sstate-cache
florian has quit [Ping timeout: 260 seconds]
<jclsn[m]>
RP: Yeah I figured that much. Also: No one works professionally with a Pi
<yolo>
jclsn[m]: want to check both download and build time, separately
<jclsn[m]>
I would also like to escape on weekends again. That is why I want to finish this stupid arts projects before spring is coming. I am never taking private projects ever again
<jclsn[m]>
yolo: Why compare downloads speeds? Seems a bit redundant
<yolo>
to pick a faster build machine out of two that is
<jclsn[m]>
You only download once
<jclsn[m]>
It is not really that important
<jclsn[m]>
Just pick the fastest computer with the most cores and RAM
troth has joined #yocto
florian has joined #yocto
<jclsn[m]>
RP: How can I find the build log for a certain recipe? I have looked a few times but can't seem to find it
<jclsn[m]>
And I am not talking about the cooker.log
<jclsn[m]>
I mean the log from the actualy package building. In qtbase there is information at the end about which features where built
<jclsn[m]>
Guess it is not printed unless you run bitbake -v?
<abelloni>
jclsn[m]: in the temp directory in the workdir of the recipe
<Saur[m]>
jclsn: You can find the build log as `tmp/work/<arch>/<pn>/<pv>/temp/log.do_compile
zen_coder has joined #yocto
<jclsn[m]>
abelloni: Thanks
florian has quit [Ping timeout: 260 seconds]
sakoman has quit [Quit: Leaving.]
florian has joined #yocto
sakoman has joined #yocto
zen_coder has quit [Ping timeout: 260 seconds]
zen_coder has joined #yocto
troth has quit [Ping timeout: 260 seconds]
agrue has quit [Remote host closed the connection]
agrue has joined #yocto
troth has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
florian has quit [Ping timeout: 256 seconds]
florian_kc has joined #yocto
<amahnui[m]>
<yolo> "is there a command like: bitbake..." <- Hello I've been trying to build using the bitbake core-image-sato command and my machine freezes all the time. My machine has 8gb of ram please is there something I can do so it doesn't freeze?
<amahnui[m]>
Because each time it does so I have to reboot the machine, and when I rerun the command, it starts back from scratch.
zen_coder has quit [Ping timeout: 260 seconds]
<vmeson>
amahnui[m]: try bitbake core-image-minimal . If that works, it's likely that you need to reduce the parallelism used by bitbake or add swap space/file.
<vmeson>
If you can catch what is being built when the crash happens, that would be good to know. See: tmp/log/cooker/qemux86-64/console-latest.log where the dir under cooker may differ.
<vmeson>
amahnui[m]: what release / branch are you using?
<amahnui[m]>
vmeson: Okay I will run it today again
<amahnui[m]>
Please I also wish to ask how much data is required for the complete build
<vmeson>
amahnui[m]: it depends on what you are building. I know that 8 GB isn't enough when I build poky/master on my RPi4... I added a 16 GB swap file and it works albeit very, very, very slowly for some parts of the build.
<vmeson>
16 GB of RAM should be okay for many builds.