From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCHv4 2/3] liblockdev: new recipe, new version of libcec requires it
Date: Thu, 06 Sep 2012 12:22:02 +0100 [thread overview]
Message-ID: <5048875A.1000205@communistcode.co.uk> (raw)
In-Reply-To: <k2a0m9$1it$1@ger.gmane.org>
On 06/09/12 12:16, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 05-09-12 17:21, ml@communistcode.co.uk schreef:
>> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>>
>> V4
>>
>> - Remove debian packaging patch, it is not needed
>>
>> Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk> ---
>> .../liblockdev/liblockdev_1.0.3.bb | 26
>> ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode
>> 100644 meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb
>>
>> diff --git a/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb
>> b/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb new file mode
>> 100644 index 0000000..be5ce44 --- /dev/null +++
>> b/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb @@ -0,0 +1,26
>> @@ +DESCRIPTION = "Manage character and block device lockfiles."
>> +HOMEPAGE =
>> "http://anonscm.debian.org/gitweb/?p=lockdev/lockdev.git;a=summary" +
>> +LICENSE = "LGPLv2.1" +LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=d8045f3b8f929c1cb29a1e3fd737b499" + +PV = "1.0.3"
> That's superfluous
>
>
>> +FILES_{PN} = "${includedir}/* \ + ${libdir}/* \ +"
> This concerns me, what is going wrong in the regular FILES_${PN} situation?
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>
> iD8DBQFQSIYUMkyGM64RGpERAq3vAJ9JrlmJY5WRA4sKpp1xs+m5jcQCdwCfSgmr
> u+zcjBy1Y1NbD+muNrVgCts=
> =11Ia
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
If I remember correctly it wasn't picking up the include files, however
that may have been before I added the incdir="${D}${includedir}" to
oe_runmake. Let me check it out.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-09-06 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 15:21 [PATCHv4 1/3] libplist: add upstream patch to fix parallel make issue ml
2012-09-05 15:21 ` [PATCHv4 2/3] liblockdev: new recipe, new version of libcec requires it ml
2012-09-05 15:41 ` Andrei Gherzan
2012-09-05 15:49 ` Jack Mitchell
2012-09-05 15:50 ` Andrei Gherzan
2012-09-06 11:16 ` Koen Kooi
2012-09-06 11:22 ` Jack Mitchell [this message]
2012-09-05 15:21 ` [PATCHv4 3/3] libcec: update libcec to latest version (1.8.1) as to include RasPi support ml
2012-09-06 8:52 ` [PATCHv4 1/3] libplist: add upstream patch to fix parallel make issue Jack Mitchell
2012-09-06 10:54 ` Koen Kooi
2012-09-06 11:17 ` Koen Kooi
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=5048875A.1000205@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox