On 5/23/20 3:04 AM, Alexander Kanavin wrote:
The problematic bit is:
# only supported by x86 and powerpc
BOOST_LIBS_append_x86 = " context coroutine"
BOOST_LIBS_append_x86-64 = " context coroutine"
BOOST_LIBS_append_powerpc = " context coroutine"
BOOST_LIBS_append_arm = " context coroutine"
BOOST_LIBS_append_aarch64 = " context coroutine"
# need consistent settings for native builds (x86 override not applied
for native)
BOOST_LIBS_remove_class-native = " context coroutine"
I'd just drop this all, and always enable the two; if they're still not
supported by some targets,
then target-specific _remove can be used.
Not unless you can ensure all other targets are taken care of when it is
enabled, which could be cumbersome, I would suggest to delete the
removal for native case, since we only have aarch64/x86 as build hosts,
it should be ok to enable it for build host.
Alex
On Sat, 23 May 2020 at 10:49, Konrad Weihmann <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
For reasons that are beyond my control I need to have boost_context
available from boost-native.
Unfortunately I didn't found a way of enabling it by a bbappend, only a
full fork of the recipe would help.
It seems to be caused by that single line
BOOST_LIBS_remove_class-native = " context coroutine" (from boost.inc)
as remove-operation is always the last in the chain of processing any
attempt to add won't work here.
Any ideas how to add it without forking the whole recipe?
Also this is another example for the ongoing discussion about remove,
??= and ?= operators in architecture list and that there might be an
alternative needed
Regards
Konrad
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#138851):
https://lists.openembedded.org/g/openembedded-core/message/138851
Mute This Topic: https://lists.openembedded.org/mt/74416620/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
