* Augmenting base files
@ 2011-08-03 11:55 Gary Thomas
2011-08-03 12:07 ` Gary Thomas
0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2011-08-03 11:55 UTC (permalink / raw)
To: Poky Project
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
I'd like to add some additional files to my build. These are
simple scripts, etc, and it makes sense to include them as part
of the base-files package for my platform.
I tried to use the attached .bbappend file for this. Sadly, after
the package fetch/unpack/patch, it has virtually nothing in it
and the build fails miserably.
ERROR: Function 'base-files: LIC_FILES_CHKSUM points to invalid file: licenses/GPL-2' failed
Looking at the work tree:
$ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69.1/
license-destdir my_script temp
Without the .bbappend, I see this in the work tree:
$ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69
deploy-ipks host.conf issue licenses package profile share temp
filesystems image issue.net motd packages-split pseudo shells usbd
fstab inputrc license-destdir nsswitch.conf pkgdata rotation shlibs
Note: I put my script in
my-layer/packages/misc/base-files-3.0.14/mytarget/my_script
If I replace this line in the .bbappend
FILESEXTRAPATHS := "${THISDIR}/${PN}-${PV}"
with these (the way I was told to do this when .bbappend first came available):
THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}/${MACHINE}"], d)}:"
then the recipe works.
Obviously, I've done something major to upset things and/or I don't understand
FILESEXTRAPATHS which I think should just add to the current list of places to
satisfy SRC_URI.
Ideas what I've done wrong?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: base-files_3.0.14.bbappend --]
[-- Type: text/plain, Size: 286 bytes --]
#
# Just tell BitBake where to find my component files
#
FILESEXTRAPATHS := "${THISDIR}/${PN}-${PV}"
PR .= ".1"
SRC_URI_mytarget_append = "\
file://my_script \
"
do_install_mytarget_append () {
install -m 0755 ${WORKDIR}/my_script ${D}${SYSCONFDIR}/my_script
}
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Augmenting base files
2011-08-03 11:55 Augmenting base files Gary Thomas
@ 2011-08-03 12:07 ` Gary Thomas
2011-08-03 15:06 ` Saul Wold
0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2011-08-03 12:07 UTC (permalink / raw)
To: Poky Project
On 2011-08-03 05:55, Gary Thomas wrote:
> I'd like to add some additional files to my build. These are
> simple scripts, etc, and it makes sense to include them as part
> of the base-files package for my platform.
>
> I tried to use the attached .bbappend file for this. Sadly, after
> the package fetch/unpack/patch, it has virtually nothing in it
> and the build fails miserably.
> ERROR: Function 'base-files: LIC_FILES_CHKSUM points to invalid file: licenses/GPL-2' failed
>
> Looking at the work tree:
> $ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69.1/
> license-destdir my_script temp
>
> Without the .bbappend, I see this in the work tree:
> $ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69
> deploy-ipks host.conf issue licenses package profile share temp
> filesystems image issue.net motd packages-split pseudo shells usbd
> fstab inputrc license-destdir nsswitch.conf pkgdata rotation shlibs
>
> Note: I put my script in
> my-layer/packages/misc/base-files-3.0.14/mytarget/my_script
>
> If I replace this line in the .bbappend
> FILESEXTRAPATHS := "${THISDIR}/${PN}-${PV}"
> with these (the way I was told to do this when .bbappend first came available):
> THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
> FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}/${MACHINE}"], d)}:"
> then the recipe works.
Sorry, this doesn't seem to be true - it still has problems either way.
The only way I've been able to get this to work at all is by changing SRC_URI
SRC_URI += "\
file://my_script \
"
No other form seems to work.
A follow up problem is that my script gets installed, but doesn't seem to be
packaged. I get a warning:
WARNING: For recipe base-files, the following files were installed but not shipped in any package:
WARNING: my_script
I thought that this line in the main recipe should include my file:
FILES_${PN} = "/"
How do I get my script to be included?
Note: this is becoming such a pain, I'll probably just write a special recipe
for it even though I think it makes sense to do it like I've been attempting...
>
> Obviously, I've done something major to upset things and/or I don't understand
> FILESEXTRAPATHS which I think should just add to the current list of places to
> satisfy SRC_URI.
>
> Ideas what I've done wrong?
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Augmenting base files
2011-08-03 12:07 ` Gary Thomas
@ 2011-08-03 15:06 ` Saul Wold
2011-08-03 15:29 ` Gary Thomas
0 siblings, 1 reply; 4+ messages in thread
From: Saul Wold @ 2011-08-03 15:06 UTC (permalink / raw)
To: Gary Thomas; +Cc: Poky Project
On 08/03/2011 05:07 AM, Gary Thomas wrote:
> On 2011-08-03 05:55, Gary Thomas wrote:
>> I'd like to add some additional files to my build. These are
>> simple scripts, etc, and it makes sense to include them as part
>> of the base-files package for my platform.
>>
>> I tried to use the attached .bbappend file for this. Sadly, after
>> the package fetch/unpack/patch, it has virtually nothing in it
>> and the build fails miserably.
>> ERROR: Function 'base-files: LIC_FILES_CHKSUM points to invalid file:
>> licenses/GPL-2' failed
>>
>> Looking at the work tree:
>> $ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69.1/
>> license-destdir my_script temp
>>
>> Without the .bbappend, I see this in the work tree:
>> $ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69
>> deploy-ipks host.conf issue licenses package profile share temp
>> filesystems image issue.net motd packages-split pseudo shells usbd
>> fstab inputrc license-destdir nsswitch.conf pkgdata rotation shlibs
>>
>> Note: I put my script in
>> my-layer/packages/misc/base-files-3.0.14/mytarget/my_script
>>
>> If I replace this line in the .bbappend
>> FILESEXTRAPATHS := "${THISDIR}/${PN}-${PV}"
>> with these (the way I was told to do this when .bbappend first came
>> available):
>> THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
>> FILESPATH =.
>> "${@base_set_filespath(["${THISDIR}/${PN}-${PV}/${MACHINE}"], d)}:"
>> then the recipe works.
>
> Sorry, this doesn't seem to be true - it still has problems either way.
>
> The only way I've been able to get this to work at all is by changing
> SRC_URI
> SRC_URI += "\
> file://my_script \
> "
> No other form seems to work.
>
> A follow up problem is that my script gets installed, but doesn't seem
> to be
> packaged. I get a warning:
> WARNING: For recipe base-files, the following files were installed but
> not shipped in any package:
> WARNING: my_script
> I thought that this line in the main recipe should include my file:
> FILES_${PN} = "/"
> How do I get my script to be included?
>
If it's simply your script, then you could try
FILES_${PN} += "my_script"
> Note: this is becoming such a pain, I'll probably just write a special
> recipe
> for it even though I think it makes sense to do it like I've been
> attempting...
>
It does make sense, not sure what's going on, but you could file a bug
Sau!
>>
>> Obviously, I've done something major to upset things and/or I don't
>> understand
>> FILESEXTRAPATHS which I think should just add to the current list of
>> places to
>> satisfy SRC_URI.
>>
>> Ideas what I've done wrong?
>>
>>
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Augmenting base files
2011-08-03 15:06 ` Saul Wold
@ 2011-08-03 15:29 ` Gary Thomas
0 siblings, 0 replies; 4+ messages in thread
From: Gary Thomas @ 2011-08-03 15:29 UTC (permalink / raw)
To: Saul Wold; +Cc: Poky Project
On 2011-08-03 09:06, Saul Wold wrote:
> On 08/03/2011 05:07 AM, Gary Thomas wrote:
>> On 2011-08-03 05:55, Gary Thomas wrote:
>>> I'd like to add some additional files to my build. These are
>>> simple scripts, etc, and it makes sense to include them as part
>>> of the base-files package for my platform.
>>>
>>> I tried to use the attached .bbappend file for this. Sadly, after
>>> the package fetch/unpack/patch, it has virtually nothing in it
>>> and the build fails miserably.
>>> ERROR: Function 'base-files: LIC_FILES_CHKSUM points to invalid file:
>>> licenses/GPL-2' failed
>>>
>>> Looking at the work tree:
>>> $ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69.1/
>>> license-destdir my_script temp
>>>
>>> Without the .bbappend, I see this in the work tree:
>>> $ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69
>>> deploy-ipks host.conf issue licenses package profile share temp
>>> filesystems image issue.net motd packages-split pseudo shells usbd
>>> fstab inputrc license-destdir nsswitch.conf pkgdata rotation shlibs
>>>
>>> Note: I put my script in
>>> my-layer/packages/misc/base-files-3.0.14/mytarget/my_script
>>>
>>> If I replace this line in the .bbappend
>>> FILESEXTRAPATHS := "${THISDIR}/${PN}-${PV}"
>>> with these (the way I was told to do this when .bbappend first came
>>> available):
>>> THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
>>> FILESPATH =.
>>> "${@base_set_filespath(["${THISDIR}/${PN}-${PV}/${MACHINE}"], d)}:"
>>> then the recipe works.
>>
>> Sorry, this doesn't seem to be true - it still has problems either way.
>>
>> The only way I've been able to get this to work at all is by changing
>> SRC_URI
>> SRC_URI += "\
>> file://my_script \
>> "
>> No other form seems to work.
>>
>> A follow up problem is that my script gets installed, but doesn't seem
>> to be
>> packaged. I get a warning:
>> WARNING: For recipe base-files, the following files were installed but
>> not shipped in any package:
>> WARNING: my_script
>> I thought that this line in the main recipe should include my file:
>> FILES_${PN} = "/"
>> How do I get my script to be included?
>>
> If it's simply your script, then you could try
>
> FILES_${PN} += "my_script"
Sorry, but that doesn't help. The resulting image is very confusing:
$ ls tmp/work/mytarget-mydistro-linux/base-files-3.0.14-r69.1/image/
my_script
which doesn't match up at all where my recipe said to put it.
>
>> Note: this is becoming such a pain, I'll probably just write a special
>> recipe
>> for it even though I think it makes sense to do it like I've been
>> attempting...
>>
> It does make sense, not sure what's going on, but you could file a bug
Done - http://bugzilla.pokylinux.org/show_bug.cgi?id=1324
>>>
>>> Obviously, I've done something major to upset things and/or I don't
>>> understand
>>> FILESEXTRAPATHS which I think should just add to the current list of
>>> places to
>>> satisfy SRC_URI.
>>>
>>> Ideas what I've done wrong?
>>>
>>>
>>>
>>> _______________________________________________
>>> poky mailing list
>>> poky@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/poky
>>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-08-03 15:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-03 11:55 Augmenting base files Gary Thomas
2011-08-03 12:07 ` Gary Thomas
2011-08-03 15:06 ` Saul Wold
2011-08-03 15:29 ` Gary Thomas
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.