Skip to contentSkip to conversation

how to (yuck) add arbitrary external files into an image?

DISCUSSION Robert P. J. Day 2 participants 3 messages Feb 22, 2015

lore
Share & tools
lore
#0 lore raw

as much as this disturbs me, i was asked about the easiest way to
add arbitrary files scattered across the development host into the final OE-generated image and, based on richard purdie's recent clarification that *everything* that is listed in SRC_URI is unloaded into WORKDIR, i suspect the easiest thing to do is create a recipe where SRC_URI lists all of those files with "file:///", and write an explicit install task that manually copies them, one at a time, into their final location in D, yes?

i don't like this at all, but if it has to be done, is this at least
the "best" way to do it?

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw

Am 22.02.2015 um 09:33 schrieb Robert P. J. Day:

Quoted 10 lines

as much as this disturbs me, i was asked about the easiest way to
add arbitrary files scattered across the development host into the final OE-generated image and, based on richard purdie's recent clarification that *everything* that is listed in SRC_URI is unloaded into WORKDIR, i suspect the easiest thing to do is create a recipe where SRC_URI lists all of those files with "file:///", and write an explicit install task that manually copies them, one at a time, into their final location in D, yes?

Quoted 2 lines

i don't like this at all, but if it has to be done, is this at least
the "best" way to do it?

I think the "best" way would be to create one recipe that collects these files and just installs them into $D. Then you could select this package in IMAGE_INSTALL as you described above.

Another way is to use a ROOTFS_POSTPROCESS_COMMAND if you only need to do this for one image.

#2 lore raw
Quoted 11 lines · Sven Ebenfeld

Am 22.02.2015 um 09:33 schrieb Robert P. J. Day:

Quoted 10 lines

as much as this disturbs me, i was asked about the easiest way
to add arbitrary files scattered across the development host into the final OE-generated image and, based on richard purdie's recent clarification that *everything* that is listed in SRC_URI is unloaded into WORKDIR, i suspect the easiest thing to do is create a recipe where SRC_URI lists all of those files with "file:///", and write an explicit install task that manually copies them, one at a time, into their final location in D, yes?

Quoted 6 lines
Quoted 2 lines

i don't like this at all, but if it has to be done, is this at
least the "best" way to do it?

I think the "best" way would be to create one recipe that collects these files and just installs them into $D. Then you could select this package in IMAGE_INSTALL as you described above.

right ... isn't that what i was describing? or are you suggesting
some variation on that? i was envisioning a single recipe with a SRC_URI loaded with "file:///" components.

Quoted 2 lines

Another way is to use a ROOTFS_POSTPROCESS_COMMAND if you only need to do this for one image.

ah, quite right, another simple option, thanks.

rday

p.s. yes, i do understand that this is a tacky thing to do. sometimes, you just need to do tacky.

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================