i'm pretty sure i know how to do this, just want to know if there's
an even easier/more elegant way.

  in current project, there is a *pile* of local content that is
identified by various recipes. so since that content is local, the
obvious starting point is for such recipes to "inherit externalsrc" to
properly identify the local source directory.

  in addition, many of those recipes represent packaging binary data
(imagine firmware files), so that there is really no meaningful
configure or compile tasks, so that further suggests inheriting
"bin_package" as well.

  finally, in some cases, there is a teeny bit of tweaking that might
be needed for the final installed content, which suggests adding:

  do_install:append()

to the mix to handle whatever little adjustments are needed.

  so given that scenario, can i reasonably summarize the right
approach as:

  inherit externalsrc
  inherit bin_package
  do_install:append()           [as needed]

finally, it doesn't seem like many of those recipes are required as
build-time dependencies, so i can just make them either RDEPENDS as
appropriate, or just IMAGE_INSTALL them for the final image.

  sound reasonable? am i overthinking this? seems fairly
straightforward.

rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193977): 
https://lists.openembedded.org/g/openembedded-core/message/193977
Mute This Topic: https://lists.openembedded.org/mt/103807270/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to