On Tue, 28 Jul 2026 at 07:17, Shinu Chandran via lists.openembedded.org <[email protected]> wrote: > # optional libraries > -PACKAGECONFIG ??= "locale python" > -PACKAGECONFIG[locale] = ",,icu" > +PACKAGECONFIG ??= "locale python icu" > +BOOST_LOCALE_ICU_DEP = "${@bb.utils.contains('PACKAGECONFIG', 'locale', > 'icu', '', d)}" > +PACKAGECONFIG[locale] = ",," > +PACKAGECONFIG[icu] = ",,${BOOST_LOCALE_ICU_DEP}" > PACKAGECONFIG[graph_parallel] = ",,,boost-mpi mpich" > PACKAGECONFIG[mpi] = ",,mpich" > PACKAGECONFIG[python] = ",,python3" > @@ -148,7 +150,7 @@ BOOST_PARALLEL_MAKE = > "${@oe.utils.parallel_make_argument(d, '-j%d')}" > BJAM_OPTS = '${BOOST_PARALLEL_MAKE} -d+2 -q \ > ${BJAM_TOOLS} \ > -sBOOST_BUILD_USER_CONFIG=${WORKDIR}/user-config.jam \ > - -sICU_PATH=${STAGING_EXECPREFIXDIR} \ > + ${@bb.utils.contains('PACKAGECONFIG', 'locale icu', > '-sICU_PATH=${STAGING_EXECPREFIXDIR}', 'boost.locale.icu=off', d)} \ > --build-dir=${B} \ > --disable-icu \
As we're passing --disable-icu, what does that do? How is it related to the icu PACKAGECONFIG? Should we perhaps name things more clearer, e.g. the newly introduced option should be 'locale-icu' and not just 'icu'? Also, I think boost.locale.icu=on should be passed when it is enabled, to explicitly avoid possible floating configurations, e.g. when upstream quietly changes the default. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#242177): https://lists.openembedded.org/g/openembedded-core/message/242177 Mute This Topic: https://lists.openembedded.org/mt/120479903/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
