|
Listing files/packages a packagegroup creates
(ctrl+enter, sorry :/) Anyways, the same (oe-pkgdata-util) approach doesn't work for identifying what files a packagegroup installs. ``` oe-pkgdata-util list-pkg-files packagegroup-core-ssh-openssh pa
(ctrl+enter, sorry :/) Anyways, the same (oe-pkgdata-util) approach doesn't work for identifying what files a packagegroup installs. ``` oe-pkgdata-util list-pkg-files packagegroup-core-ssh-openssh pa
|
By
Alan
· #44766
·
|
|
Listing files/packages a packagegroup creates
Hi, when searching for the files a package creates I find it very practical to use `oe-pkgdata-util`. i.e. oe-pkgdata-util list-pkg-files busybox However the same method doesn't work when applied to p
Hi, when searching for the files a package creates I find it very practical to use `oe-pkgdata-util`. i.e. oe-pkgdata-util list-pkg-files busybox However the same method doesn't work when applied to p
|
By
Alan
· #44765
·
|
|
Best practices for tokens/passwords that can't be versioned
Thanks for the feedback. This is a very interesting use case. By default you want to allow ssh access for the developer who built the image, cool :) <enrico.scholz@...> wrote:
Thanks for the feedback. This is a very interesting use case. By default you want to allow ssh access for the developer who built the image, cool :) <enrico.scholz@...> wrote:
|
By
Alan
· #43519
·
|
|
Best practices for tokens/passwords that can't be versioned
Yes! :) That is what I ended up doing in the end, thanks. Be Well, Alan
Yes! :) That is what I ended up doing in the end, thanks. Be Well, Alan
|
By
Alan
· #43517
·
|
|
Best practices for tokens/passwords that can't be versioned
Thanks Erik, guess that could work to and seems cleaner than the env variables. It still leaves the question how to move that content into a static file. For example if in the end the recipe should in
Thanks Erik, guess that could work to and seems cleaner than the env variables. It still leaves the question how to move that content into a static file. For example if in the end the recipe should in
|
By
Alan
· #43493
·
|
|
Best practices for tokens/passwords that can't be versioned
Hi, am looking for opinions on how to deal with recipes that depend on file content that can't be versioned. i.e. The logging service on the embedded device needs to have a certain private key or toke
Hi, am looking for opinions on how to deal with recipes that depend on file content that can't be versioned. i.e. The logging service on the embedded device needs to have a certain private key or toke
|
By
Alan
· #43490
·
|
|
CONFFILES journey form source dir to rootfs
What's the reason for not seeing that in `bitbake -e systemd`? Be Well, Alan
What's the reason for not seeing that in `bitbake -e systemd`? Be Well, Alan
|
By
Alan
· #43186
·
|
|
CONFFILES journey form source dir to rootfs
Hi, I'm trying to understand how a conf file finds its way from source to the rootfs. The example is use is `journald.conf` from systemd. The file originates from systemd source: work/cortexa7hf-neon-
Hi, I'm trying to understand how a conf file finds its way from source to the rootfs. The example is use is `journald.conf` from systemd. The file originates from systemd source: work/cortexa7hf-neon-
|
By
Alan
· #43183
·
|
|
Check final recipe state
Hi, looking for a way to inspect the appearance of the final recipe after all the .bbappend files have been applied. Example: meta-openembedded/meta-oe/recipes-extended/rsyslog/rsyslog_8.29.0.bb gets
Hi, looking for a way to inspect the appearance of the final recipe after all the .bbappend files have been applied. Example: meta-openembedded/meta-oe/recipes-extended/rsyslog/rsyslog_8.29.0.bb gets
|
By
Alan
· #43118
·
|
|
(How) did you script bitbake/set up nightly builds?
It seems the call doesn't work correctly with dash (ls -la /bin/sh): subprocess.call(". oe/oe-init-build-env; ls", shell = True) /bin/sh: 51: .: Can't open root_dir/scripts/oe-buildenv-internal Specif
It seems the call doesn't work correctly with dash (ls -la /bin/sh): subprocess.call(". oe/oe-init-build-env; ls", shell = True) /bin/sh: 51: .: Can't open root_dir/scripts/oe-buildenv-internal Specif
|
By
Alan
· #42357
·
|
|
(How) did you script bitbake/set up nightly builds?
Great, that's quite clean. Opting for that, thanks Ross. Be Well, Alan
Great, that's quite clean. Opting for that, thanks Ross. Be Well, Alan
|
By
Alan
· #42342
·
|
|
(How) did you script bitbake/set up nightly builds?
Fair enough, I gave an example with a simple workaround. :) But you do have a point there, if I'm getting you answer right on a broader level. Is it something like this? > Instead of setting the envir
Fair enough, I gave an example with a simple workaround. :) But you do have a point there, if I'm getting you answer right on a broader level. Is it something like this? > Instead of setting the envir
|
By
Alan
· #42340
·
|
|
(How) did you script bitbake/set up nightly builds?
Thanks Ross this is what more or less what I'm doing. What I haven't found a way to do from python is making modifications from the initialized build directory. I'd like to do that to change things in
Thanks Ross this is what more or less what I'm doing. What I haven't found a way to do from python is making modifications from the initialized build directory. I'd like to do that to change things in
|
By
Alan
· #42338
·
|
|
(How) did you script bitbake/set up nightly builds?
Hi, am just in the process of forming a base for automated nightly builds. The goal is to have the build process run every night and report what the status was. I've opted for python for all the condi
Hi, am just in the process of forming a base for automated nightly builds. The goal is to have the build process run every night and report what the status was. I've opted for python for all the condi
|
By
Alan
· #42335
·
|
|
Doubts about image "equalness"
Hey Matthias, thanks for the response I don't see it as that big of a problem. In our case it would end up mounting the production image and editing config files to i.e. enable ssh, point to a differe
Hey Matthias, thanks for the response I don't see it as that big of a problem. In our case it would end up mounting the production image and editing config files to i.e. enable ssh, point to a differe
|
By
Alan
· #42195
·
|
|
Doubts about image "equalness"
Hi, I'm hoping to get opinions on a doubt regarding a certain yocto related problem. We have a following images in place: * production-image.bb * core features, max security * beta-image.bb * require
Hi, I'm hoping to get opinions on a doubt regarding a certain yocto related problem. We have a following images in place: * production-image.bb * core features, max security * beta-image.bb * require
|
By
Alan
· #42178
·
|
|
Preventing wic for running for an initramfs image
Hi, I'm setting up an initramfs image for an ARM board. The minimal recipe I got to build the image is: # Simple initramfs image. Mostly used for live images. DESCRIPTION = "Small image capable of boo
Hi, I'm setting up an initramfs image for an ARM board. The minimal recipe I got to build the image is: # Simple initramfs image. Mostly used for live images. DESCRIPTION = "Small image capable of boo
|
By
Alan
· #42038
·
|
|
wic appending ".1" to a file name on multiple images build
Yeah, a deep dive it is then. :) Am just trying to print from the code using the Python debugger (as used in the source file). self._log.debug("Print this") but it's not printing anything even when ru
Yeah, a deep dive it is then. :) Am just trying to print from the code using the Python debugger (as used in the source file). self._log.debug("Print this") but it's not printing anything even when ru
|
By
Alan
· #41303
·
|
|
Image specific configuration files
Yes, much better phrasing: > A single bitbake invocation always builds a single distro for a specific target machine Thanks
Yes, much better phrasing: > A single bitbake invocation always builds a single distro for a specific target machine Thanks
|
By
Alan
· #41299
·
|
|
wic appending ".1" to a file name on multiple images build
Hi, I'm creating two images with the single bitbake command and on inherits the other (production, and a dev which "require production"). Building them at the same time causes an issue: Traceback (mos
Hi, I'm creating two images with the single bitbake command and on inherits the other (production, and a dev which "require production"). Building them at the same time causes an issue: Traceback (mos
|
By
Alan
· #41298
·
|