|
#dunfell Path to sources in debugfs
#dunfell
I think its not a general problem with autotool based projects doing out of tree builds but just with sqlite3 package. Perhaps you might want to look at compiler commandline options being passed to sq
I think its not a general problem with autotool based projects doing out of tree builds but just with sqlite3 package. Perhaps you might want to look at compiler commandline options being passed to sq
|
By
Khem Raj
· #54964
·
|
|
file package dependency
I think looking into buildhistory metadata might give some hints, it stores the information about image to package dependencies in a dotty file which you can either open in a viewer or text editor and
I think looking into buildhistory metadata might give some hints, it stores the information about image to package dependencies in a dotty file which you can either open in a viewer or text editor and
|
By
Khem Raj
· #54962
·
|
|
virtual/egl on Raspberry Pi 4
that should have worked well for userland recipe to provide it. Maybe you need to set VC4GRAPHICS = "" in local.conf <GWilson@...> wrote:
that should have worked well for userland recipe to provide it. Maybe you need to set VC4GRAPHICS = "" in local.conf <GWilson@...> wrote:
|
By
Khem Raj
· #54961
·
|
|
virtual/egl on Raspberry Pi 4
It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something Are you compiling 32bit m
It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something Are you compiling 32bit m
|
By
Khem Raj
· #54947
·
|
|
virtual/egl on Raspberry Pi 4
it should be provided by userland package if you are using closed source graphics driver.
it should be provided by userland package if you are using closed source graphics driver.
|
By
Khem Raj
· #54944
·
|
|
Meta-raspberrypi - how to configure device tree for MCP251x
can you check boot/config.txt and see fi your changes are there in your target ?
can you check boot/config.txt and see fi your changes are there in your target ?
|
By
Khem Raj
· #54941
·
|
|
Shared lib symlinks in target image
Libraries have another symlink which looks something like libfoo.so.1 and 2 etc that is the one which should be used by apps
Libraries have another symlink which looks something like libfoo.so.1 and 2 etc that is the one which should be used by apps
|
By
Khem Raj
· #54938
·
|
|
Shared lib symlinks in target image
unversioned symlinks should not be used they are there to be used for linking during build time. Unless you need to do builds on targets you really do not need them so explain you usecase. Are you try
unversioned symlinks should not be used they are there to be used for linking during build time. Unless you need to do builds on targets you really do not need them so explain you usecase. Are you try
|
By
Khem Raj
· #54935
·
|
|
[OE-core] Incorrect systemd timer
perhaps use OnCalendar=*-*-* *:*:00
perhaps use OnCalendar=*-*-* *:*:00
|
By
Khem Raj
· #54879
·
|
|
Cross-compiling or compiling on target VM?
there are different possibilities you have with all great tooling you get with yocto project, I think you have made a good choice. inherently Yocto project is a cross compiling infrastructure so lot o
there are different possibilities you have with all great tooling you get with yocto project, I think you have made a good choice. inherently Yocto project is a cross compiling infrastructure so lot o
|
By
Khem Raj
· #54847
·
|
|
"stack smashing detected" when building aarch64 kernel
its hard to say what might be going on. Perhaps enable builds with V=1 so you can see if its always failing to compile at same file. or atleast you can get one file where it fails then you can use pre
its hard to say what might be going on. Perhaps enable builds with V=1 so you can see if its always failing to compile at same file. or atleast you can get one file where it fails then you can use pre
|
By
Khem Raj
· #54831
·
|
|
gcov support for target in Yocto
IMAGE_INSTALL += "gcov gcov-symlinks"
IMAGE_INSTALL += "gcov gcov-symlinks"
|
By
Khem Raj
· #54830
·
|
|
[meta-rockchip][PATCH] use uuid instead of hard-coding root device
are you both using systemd or sysvinit
are you both using systemd or sysvinit
|
By
Khem Raj
· #54829
·
|
|
Using bitbake with external SDK
#sdk
#zeus
#toolchain
if its eSDK then you can, with standard application SDK not so much.
if its eSDK then you can, with standard application SDK not so much.
|
By
Khem Raj
· #54820
·
|
|
googletest shared library
look into package-split/ directory inside googletest build area and see how things changes when you use SOLIBS option. I wonder why its ignoring .h files
look into package-split/ directory inside googletest build area and see how things changes when you use SOLIBS option. I wonder why its ignoring .h files
|
By
Khem Raj
· #54819
·
|
|
[meta-rockchip][PATCH] use uuid instead of hard-coding root device
yes was seeing same. Can you turn this into a patch and send?
yes was seeing same. Can you turn this into a patch and send?
|
By
Khem Raj
· #54802
·
|
|
Permission denied with NFS shared download and sstate-cache
its trying to create the file with 0600 mask. I wonder whats your global umask set to. and perhaps the user is not same when bitbake it running ?
its trying to create the file with 0600 mask. I wonder whats your global umask set to. and perhaps the user is not same when bitbake it running ?
|
By
Khem Raj
· #54796
·
|
|
googletest shared library
The .h files will be in dev pkg in this case googletest-dev what happens if you add googletest to TOOLCHAIN_TARGET_TASK
The .h files will be in dev pkg in this case googletest-dev what happens if you add googletest to TOOLCHAIN_TARGET_TASK
|
By
Khem Raj
· #54794
·
|
|
Sharing sstate cache across build nodes
yes if you use uninative ( which is default in poky) then it should be able to share across multiple build hosts. if you preserve PR server data then you should be good. sstate can be regenerated.
yes if you use uninative ( which is default in poky) then it should be able to share across multiple build hosts. if you preserve PR server data then you should be good. sstate can be regenerated.
|
By
Khem Raj
· #54735
·
|
|
How to build yocto image with Desktop
#dunfell
there is core-image-x11 which will be bareminimal and core-image-weston if you want to use wayland/weston based desktop. if you like XFCE for desktop then close meta-openembedded and add meta-oe and m
there is core-image-x11 which will be bareminimal and core-image-weston if you want to use wayland/weston based desktop. if you like XFCE for desktop then close meta-openembedded and add meta-oe and m
|
By
Khem Raj
· #54728
·
|