here's the next head-scratching oddity i just ran across in the current layer (and there's more weirdness on its way).
perusing a recipe only to see: FILESPATH =+ "${COMMON_STUFF_DIR}:" SRC_URI += "file://file1 file://file2 file://file 3 ... etc ..." ok ... apparently, there are a number of recipes that want access to some small set of common files, so the solution(?) was to put those common files in some (out-of-layer) directory, and prepend to FILESPATH in each of those recipe files so that SRC_URI could find them. i am not going to ask if this is some wickedly clever trick, since it can't be. it just can't. even stranger, one of the common files was a configuration script that contributed the line: . config.sh to the top of a number of common tasks like do_configure, do_compile, do_install and so on. a similar tactic was to find this line in a class file: FILESEXTRAPATHS_prepend := "${COMMON_STUFF_DIR}:" my head hurts. first, if i needed to do something in common at the beginning of some basic tasks, i'd invent a bbclass file that "_prepend"ed to those tasks, and just inherit it when necessary. as for a number of recipes needing access to common files for any reason, well, thoughts? my first thought is to encapsulate those files in a separate recipe, then make that recipe a build dependency so that those files would be available from the sysroot, but i'm sure there are better ideas. are there any OE recipes that demonstrate this sort of thing? because extending FILESPATH to arbitrary out-of-layer directories just makes me want to strangle kittens. rday
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#149801): https://lists.openembedded.org/g/openembedded-core/message/149801 Mute This Topic: https://lists.openembedded.org/mt/81536884/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-