Thanks folks, IMAGE_GEN_DEBUGFS was exactly what I was looking for. --wpd

I know I can do $ bitbake base-image -cpopulate_sdk and distribute the resulting SDK to developers (myself included). But suppose I've just built and deployed an image and want to debug a core file ge

Never mind. I found it. I did something like: EXTERNAL_FILE="${@bb.fetch.decodeurl(d.getVar('EXTERNAL_URL',True))[2]}" do_compile() { do -something-with $(basename ${EXTERNAL_URL}) } I would still be

I have a recipe that looks something like this (I'm simplifying a bit here): SRC_URI += "${EXTERNAL_URL}" do_compile() { do -something -with $(basename ${EXTERNAL_URL} .ext) } where EXTERNAL_URL is su

On Wed, Mar 11, 2020 at 1:26 PM Patrick Doyle via Lists.Yoctoproject.Org <wpdster=gmail.com@...> wrote: Apparently, the answer is that I should use "inherit adduser" instead of "inh

I may be overthinking/overtweaking this but... I have a recipe with that creates a number of executables, one of which is a daemon. I have split that daemon off into its own separate package using the

I haven't tried this with glibc/mips with the same settings, but I expect it would work in that scenario, as I see support for MIPS_RLD_MAP_REL in the glibc sources. If anybody is interested, I have a

<richard.purdie@...> wrote: Thank you. That is, indeed, what I want. It demonstrates the same problem, and I can debug it. Aside... it's quite a mind bending experience to debug gdb wi

Does anybody have any tips or tricks for how I might debug the (cross-canadian) gdb built by Yocto's SDK? I need to add some printf's to the gdb code to help track down why something isn't working, bu

i was just reviewing a recipe I wrote a month or two ago and saw that I wrote: do_compile() { python3 ${WORKDIR}/assemble-tsk-blob.py -o tsk-blob -d ${DEPLOY_DIR_IMAGE}/foo -t ${DEPLOY_DIR_IMAGE}/bar

Thank you. That feels like the better answer all around. Ultimately, that's where I was going, but hadn't thought of the fact that I only really need this data on my native build environment. --wpd

Oops... I just noticed the typo(s) in my recipe... I wasn't installing the contents of my ${WORKDIR} in ${D}${datadir}/keys the way I thought I was... all I was doing was creating empty directories. T

I have a set of data files (cryptographic keys) that I would like to share among several recipes in my build. They won't go into the rootfs, but they will be used by multiple recipes that construct th

Is this a solved problem? If so, what is the correct solution? Here are some more details of the problem statement... I want to verify that my read-only rootfs has not been modified when I boot. So I

How do I use the reproducible_build class to create a reproducible u-boot? I tried adding inherit reproducible_build to my u-boot recipe, but when I do that, I generate errors of the form: ERROR: When

What I neglected to say was that a colleague of mine had recently added crda to our build as well, and that recipe has an explicit RDEPENDS on "udev". I did spend an interesting day learning about the

Did that get your attention? :-) I am trying to understand why eudev gets pulled into my build, where it wasn't part of it before. I recently added an initramfs to my build by setting: INITRAMFS_IMAGE

<gabbla.malist@...> wrote: Thanks again for your thoughts, ideas, and conversation. Based on this conversation and further research around the web, it seems like defining a new MACHINE is the be

<gabbla.malist@...> wrote: Hi Gabriele, Thank you again so much for your help! My use case is as follows: I need to create an image that will go on a USB stick that we use when we manufacture ou

<gabbla.malist@...> wrote: Hi Gabriele, I wondered about that, but I get confused about the MACHINE concept in Yocto/OE/bitbake... 1. If I define a new machine, but I have a lot of recipes condi