You should open a ticket with eudev though or submit a patch there.
Alex
On Thu 6. Jun 2024 at 12.41, Lukas Weiß via Lists.Yoctoproject.Org
wrote:
> Sorry, was busy with something else.
>
> Thanks for the hint. I think, i found the reason: The Links is already
> broken on install. Its part of t
Sorry, was busy with something else.
Thanks for the hint. I think, i found the reason: The Links is already broken
on install. Its part of the Autotools Install of the eudev project
(src/libudev/Makefile.in):
>
>
>
> install-exec-hook:
> libname=libudev.so; if test "$(libdir)" != "$(rootlibd
On Wed, 29 May 2024 at 18:13, Lukas Weiß via Lists.Yoctoproject.Org
wrote:
> how can i see if the link is broken on build or packaging? Since the path of
> the broken link can't be known on build process (it was entered in install
> process of SDK sh installer), i will not be able to find it som
Hallo Alexander,
how can i see if the link is broken on build or packaging? Since the path of
the broken link can't be known on build process (it was entered in install
process of SDK sh installer), i will not be able to find it somewhere in logs
or env. It must be some kind of variable that is
Is the link correct when nativesdk-udev is built and packaged or is it
already broken at that point?
Generally you should take the trouble to spin up qemu and run the tests in
that.
Alex
On Wed 29. May 2024 at 15.27, Lukas Weiß via lists.yoctoproject.org
wrote:
> Hi together,
>
> i have a ques
Hi together,
i have a question about Yocto SDK generation. We use the Yocto-SDK not only for
generation of target binaries outside the Yocto Build process, but also for
generation of the same binaries *for the host* (nativesdk). This way we are
able to run our applications as Simulations or Uni
