I like the idea of the class-target, but we were not able to get it
running in our environment for now, even when removing the patch file.
Everything looks correct, but the "find_package..." in cmake is not able
to find the capnp binaries. It would be nice to have this working since
when then could remove our ugly hack. ;-)
On 25.02.25 10:44, Gyorgy Sarvari via lists.openembedded.org wrote:
Hmmm, the native part wasn't supposed to be touched... but now that you
mention, I think I see where my error is.
Thanks for the feedback, will try to look into this later today (unless
someone else is faster). Not sure about the class-target part, but will
try to check on that too, if I can find a more graceful solution.
On 25.02.25 10:24, Thomas Schlien wrote:
Hi,
we actually stumbled upon this issue because the patch also removes the
binaries from the native package. As a result, our software—which
requires the native binaries for compilation—no longer builds. I had to add
SRC_URI:remove = "file://0001-Don-t-check-usr-bin-content-from-cmake.patch"
to a capnproto_%.bbappend in our layer to get it working again.
One could also imagine use cases where having the capnp tools available
on the target system would be beneficial. Therefore, I believe that not
installing the binaries in the target package should be configurable.
Best regards,
Thomas
On 03.02.25 13:11, Gyorgy Sarvari via lists.openembedded.org wrote:
While looking into Ross' feedback about the first version, I realized
that my
sed regex didn't only have superficial problems (namely being an
eyesore, and
likely brittle), but it also only solved a part of the problem - it
allowed to
link to the cross-compiled libs, but code-generation during class-target
compilation from capnproto definitions was still broken.
This patch supposed to remediate this too.
If you think that having a new class is overcomplicating the issue, I
can be easily
convinced about it (but please leave an alternative suggestion also).
There is 1 known caveat however: if someone would want to install the
binaries
from ${bindir} on the target machine, that won't work after this
change. (Can't
really think of any reasons however, why would one do that - this is
not a user-application.)
Let me know if there's anything you'd like to change in this patch.
--
Dr.-Ing. Thomas Schlien
Ferncast GmbH
Gallierstr. 41a, 52074 Aachen
Germany
Phone: +49 241 99034567
Web: www.ferncast.de
--
CEO: Detlef Wiese
Court of Registration: Amtsgericht Aachen
Commercial Register: HRB 22350
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#115567):
https://lists.openembedded.org/g/openembedded-devel/message/115567
Mute This Topic: https://lists.openembedded.org/mt/110969312/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
