Ok I figured it out. I needed to use TOOLCHAIN_HOST_TASK not TOOLCHAIN_HOST_TASK_ESDK. i.e.
TOOLCHAIN_HOST_TASK += " nativesdk-test-py " I guess the eSDK incorporates the SDK settings as well. The documentation is very misleading when it explicitly says you should use TOOLCHAIN_HOST_TASK_ESDK. https://docs.yoctoproject.org/ref-manual/variables.html#term-TOOLCHAIN_HOST_TASK_ESDK When in fact you can’t set TOOLCHAIN_HOST_TASK_ESDK at all. Perhaps the variable should be removed from the glossary? From: [email protected] <[email protected]> On Behalf Of Sutton, Chris (FP) - IC via lists.openembedded.org Sent: 15 August 2023 16:14 To: [email protected] Subject: [EXTERNAL] [OE-core] nativesdk recipe not added to esdk WARNING: Email originated from an EXTERNAL source. Do NOT click links, open attachments or reply unless you recognize sender and know the content is safe. Hi, I have a recipe - test-py.bb - that contains: BBCLASSEXTEND = "native nativesdk". FILES:${PN} += " one.py two.py" do_install() { install -D ${WORKDIR}/git/Core/scripts/one.py "${D}$bindir}/one.py" install -D ${WORKDIR}/git/Core/scripts/two.py "${D}$bindir}/two.py" } I want to have those python files made available in the $PATH of the esdk. So in the local.conf I have: TOOLCHAIN_HOST_TASK_ESDK += " nativesdk-test-py " I build the full version of the esdk. I install the eSDK and run "devtool sdk-install test-py" I do a search but I cannot find one.py/two.py anywhere in the esdk install. I notice that Yocto is not generating a nativesdk-test-py recipe under work/tmp/x86_64-nativesdk-pokysdk-linux. I though this was the purpose of adding nativesdk with BBCLASSEXTEND? I notice that populate_sdk_ext.bbclass hardcodes the TOOLCHAIN_HOST_TASK_ESDK variable to meta-environment-extsdk-${MACHINE}. Surely this is overwriting any values I use the local.conf. I don't fully understand the meta-environment-extsdk.bb mechanism but I get the impression this is the key to adding something to the esdk? Also is there a way to confirm which packages have been added to the esdk? It seems to be obfuscated behind the meta-environment-extsdk recipe. CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving. L3Harris Technologies UK Limited is a private company registered in England with the company number 11111631 whose registered office is at 100 New Bridge Street, London, United Kingdom, EC4V 6JA. For information on our Privacy & Cookie Policies, please visit our website: https://www.l3harris.com/en-gb/privacy-policy
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#186328): https://lists.openembedded.org/g/openembedded-core/message/186328 Mute This Topic: https://lists.openembedded.org/mt/100759936/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
