From: Saul Wold <sgw@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Augmenting base files
Date: Wed, 03 Aug 2011 08:06:52 -0700 [thread overview]
Message-ID: <4E39640C.4030005@linux.intel.com> (raw)
In-Reply-To: <4E3939ED.5070608@mlbassoc.com>
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
>
next prev parent reply other threads:[~2011-08-03 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 11:55 Augmenting base files Gary Thomas
2011-08-03 12:07 ` Gary Thomas
2011-08-03 15:06 ` Saul Wold [this message]
2011-08-03 15:29 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E39640C.4030005@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.