After running testimage there are some python left overs at
lib/oeqa/runtime/cases/__pycache__/
Signed-off-by: Adrian Freihofer
---
.gitignore | 7 +++
1 file changed, 7 insertions(+)
create mode 100644 .gitignore
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000
Hi Lukasz
Also our test infrastructure expects an exit value not equal to 0 in
case of a failed test.
Regards,
Adrian
On Wed, 2021-07-21 at 11:46 +0200, ?ukasz Majewski wrote:
> Up till now ptest-runner2 returns number of failed tests with its
> exit status code. Such use case is not
On Wed, 2023-11-01 at 16:19 +0100, Alexander Kanavin via
lists.openembedded.org wrote:
> On Wed, 1 Nov 2023 at 15:18, wrote:
> > We are currently experimenting with replacing the eSDK installer
> > with
> > the bitbake build environment for our users. Part of this
> > transformation is, of
Hi Richard, hi Alex
On Mon, 2023-10-30 at 14:07 +, Richard Purdie wrote:
> On Mon, 2023-10-30 at 14:50 +0100, Alexander Kanavin wrote:
> > On Thu, 14 Sept 2023 at 14:56, Richard Purdie
> > wrote:
> > > There are design elements to this work. We need to work out how
> > > we can
> > > make
Hi Alex, hi Richard
The discussion looks really interesting. I would like to contribute
some comments from the point of view of a rather naive user and try to
understand the workflows for which these improvements would be
beneficial also on a bigger picture.
On Thu, 2023-09-14 at 20:51 +0200,
On Wed, 2023-11-01 at 18:28 +0100, Alexander Kanavin wrote:
> On Wed, 1 Nov 2023 at 16:45, wrote:
> > I think these differences between SDK and bitbake environment are
> > no
> > longer required and they have been problematic. I would try to make
> > the
> > bitbake environment usable like the
On Sat, 2023-11-04 at 11:09 +, Richard Purdie wrote:
> On Sat, 2023-11-04 at 11:29 +0100, adrian.freiho...@gmail.com wrote:
> > Hi Alex, hi Richard
> >
> > After some internal discussions, I would like to clarify my
> > previous
> > answers on this topic.
> >
> > * Usually there are two
Hi Alex, hi Richard
After some internal discussions, I would like to clarify my previous
answers on this topic.
* Usually there are two different workflows
- application developers: could use an SDK with a locked sstate-cache.
- Yocto/BSP developers: need an unlocked SDK. They change
Hi
Would it be possible to extend the
https://wiki.yoctoproject.org/wiki/System_Update table with compatible
backends? Ideally the license of the backends should also be
transparent. OE/Yocto should not end up with a vendor lock in when it
comes to a standard update mechanism. In the end it's
Hi Darek
Making the recipe compiling for cross and native and adding a DEPENDS from
cross to native seems to be the cleanest and most Yocto-ish way to me.
Alternatively this patch would allow to run cross compiled executables with
Qemu in the cmake project
Did you already consider to write the credentials in a .netrc file?
Regards
Adrian
schrieb am Fr., 20. Okt. 2023, 13:55:
> Greetings!
> I try to use gitsm fetcher to fetch bitbucket repository with read-only
> https access token. SRC_URI looks like this
>
> SRC_URI =
>
The best would probably be to improve the Makefile to install the files to
standard paths such as /usr instead of /usr/local. /usr/local is usually
used for not packaged files and therefore not handled by the default FILES
package splitting rules of Yocto.
Ideally there would be a PREFIX variable
On Sat, 2023-08-19 at 19:21 +0200, Alexander Kanavin wrote:
> It’s well possible that emulating the arm hardware is not needed, in
> this case x86_64 is vastly better, as it will run at native speeds
> with kvm. When qemu translates arm to x86, the performance drops 10x
> or more.
>
> The issue
Hi Jens-Christoph
By when do you need it?
The article should probably be written in German, correct?
Regards,
Adrian
On Tue, 2022-04-26 at 10:25 +, Jens-Christoph Brendel wrote:
> Hello,
>
> We, the German Linux magazine, are planning a focus on Linux
> distributions for the IoT in the
Hi,
I guess the sw-description file must be added to the Image recipe not to
swupdate.bb.
Note: There is a specific mailing list for swupdate.
Regards,
Adrian
Mahendra Sondagar schrieb am So., 25. Sept.
2022, 20:01:
> Thanks, Chetan for swift reply :)
>
> However, swupdate unable to fetch
Hi Alex, hi José
The meta-lts-mixin layers for dunfell have a major disadvantage:
Replacing the go tool-chain breaks more or less all recipes from meta-
virtualization and potentially other layers.
I think with go it should be possible to have a meta-lts-mixin layer
which adds support for
Hi Simon
I guess in the deploy folder (build/tmp/deploy/...) you will find a tar
archive which can be used with e.g. docker import.
If you need to upload the OCI image to a container registry skopeo
might be used somehow like that:
bitbake "skopeo-native:do_addto_recipe_sysroot"
On Thu, 2023-07-06 at 13:12 +0300, Anders Montonen wrote:
>
>
> > On 6 Jul 2023, at 12:55, MOHAMMED HASSAN
> > wrote:
> >
> > On Thu, Jul 6, 2023 at 02:29 AM, Adrian Freihofer wrote:
> > > Hi Hassan
> > >
> > > It's a bit hard t
Hi Hassan
It's a bit hard to guess what you are really doing. The bb is a fork
from a quite old version when it was still using the autotools. Now we
use meson.
The check for rl_echo_signal_char came into NetworkManager 8 years ago
On Thu, 2023-07-06 at 02:54 -0700, MOHAMMED HASSAN wrote:
> On Thu, Jul 6, 2023 at 02:29 AM, Adrian Freihofer wrote:
> > Hi Hassan
> Hi Adrian,
> Thanks for your reply.
> > It's a bit hard to guess what you are really doing. The bb is a
> > fork
> > from a quite ol
way to register this out-of-tree fetcher module so
> tinfoil/devtool can “see” them?
>
> Cheers
> Konrad
>
>
>
>
--
Adrian Freihofer
Gschwaderweg 29
8610 Uster
+41 76 503 37 98
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Re
Hi Steve
Maybe this discussion provides some hints for you
https://lists.openembedded.org/g/openembedded-devel/topic/98852053#102633
Regards
Adrian
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60165):
On Sun, 2023-07-30 at 04:00 -0700, daniel_herrman...@web.de wrote:
> Hello,
> I have a problem enabling a simple systemd service.
> I need a manual "systemctl enable" once after boot to enable my
> service.
> If anybody has an idea, it would be very cool.
> Here are my files.
> distro conf:
>
It depends on your use case, but might be
that
https://docs.yoctoproject.org/sdk-manual/extensible.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
could work for you. With recent Yocto versions populate_sdk_ext is no
longer needed to get the eSDK environment.
On Tue, 2024-01-02 at 09:24 +0200, Mikko Rapeli wrote:
> Hi,
>
> On Sat, Dec 23, 2023 at 02:47:36AM -0800, fabian.hanke via
> lists.yoctoproject.org wrote:
> > Hello Yocto community,
> >
> > we must provide a SBOM for our Yocto based product which will then
> > be used for (internal) CVE
Hi Marta
>
> The discussion in this thread is in fact related to what we have in
> sessions
> about SRTools. Would you be willing to join?
>
I remember that the meetings were announced via the mailing lists. But
I can no longer find them and they are not listed on
> I found the following RFC and I apply that and seems to be fine
> https://lore.kernel.org/all/20220622103312.1098389-3-a...@linutronix.de/T/#m7eadf6c722410f5b233ebba9fc700a895af9f052
> How can we proceed?
We also picked just these patches back to kirkstone. This works without
negative impact.
27 matches
Mail list logo
