All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: rpurdie@rpsys.net
Cc: openembedded-devel <openembedded-devel@openembedded.org>
Subject: Re: RFC: "Virtual" native and sdk recipes
Date: Wed, 14 Jan 2009 01:03:39 +0100	[thread overview]
Message-ID: <496D2BDB.6030603@gmx.net> (raw)
In-Reply-To: <1230827114.5320.42.camel@dax.rpnet.com>

[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]

Hi Richard,
I somehow missed this thread.

Richard Purdie schrieb:
> Proposal Step A:
> 
> Having to set:
> 
> FILESDIR = "${@os.path.dirname(bb.data.getVar('FILE',d,1))}/foo-${PV}"
> 
> and
> 
> S = "${WORKDIR}/foo-${PV}
> 
> is fairly pointless and it would be nice the the defaults just did the
> right thing. 
> 
> http://git.pokylinux.org/cgit.cgi/poky/commit/?h=experimental-virtualnative&id=b8f0510a5567f6d1b90934fe513fd40423f11086
> 
> is a patch introducing BASEPN which is PN with a range of specified
> suffixes removed (-native, -cross-sdk, -cross, -sdk as specified by
> SPECIAL_PKGSUFFIX).
> 
> FILESPATH and S can then be constructed with BASEPN instead of PN
> removing the need to need to hardcode them:
> 
> http://git.pokylinux.org/cgit.cgi/poky/commit/?h=experimental-virtualnative&id=ed829661d51b8f23628e97404ed507c2e56d8495
> 
> This reduces my hypothetical example to:
> 
> foo/foo.inc:
> 
> SRC_URI = "http://somwehere/${BASEPN}-${PV}.tar.bz2 \
>            file://some.patch;patch=1"
> inherit autotools
> 
> foo/foo-native_1.0.bb:
> require foo_${PV}.bb
> inherit native
> 
> The above proposal is worthwhile in itself alone.
Like koen said we have something like this in OE already but your
implementation looks better:

a) BASEPN, BASEP instead of BPN, BP:
This is less prone to be confused with "B". Furthermore I just tried to
put the BPN code into my local Poky and it turned out that somehow BPN
and BP are not set by the 'base_package_name' although its the same code
as in OE's org.oe.dev. There not many packages in OE which use BPN/BP so
we can quickly rename those that do.

I use BP/BPN more extensively in Jalimo but I already have a patch to
fix this.

b) Use of SPECIAL_PKGSUFFIX variable to define known suffixes
In OE's implementation this is hardcoded in the function code. Not so
nice but heck I am no python coder. :$

Regards
Robert



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

      parent reply	other threads:[~2009-01-14  0:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 16:25 RFC: "Virtual" native and sdk recipes Richard Purdie
2009-01-01 18:11 ` Koen Kooi
2009-01-01 20:07   ` Richard Purdie
2009-01-01 18:25 ` Tom Rini
2009-01-01 20:11   ` Richard Purdie
2009-01-01 22:02     ` Tom Rini
2009-01-02  1:11       ` Richard Purdie
2009-01-02  4:37         ` Native/Cross/SDK rethink (Was: Re: RFC: "Virtual" native and sdk recipes) Tom Rini
2009-01-05 14:31           ` Esben Haabendal
2009-01-05 15:42             ` Tom Rini
2009-01-05 17:29             ` Koen Kooi
2009-01-05 19:53               ` Tom Rini
2009-01-06 20:51               ` Esben Haabendal
2009-01-07  0:14                 ` Richard Purdie
2009-01-07  0:45                   ` Tom Rini
2009-01-08 22:59                   ` Leon Woestenberg
2009-01-09  0:54         ` RFC: "Virtual" native and sdk recipes Richard Purdie
2009-01-09  1:16           ` Tom Rini
2009-01-12 19:09             ` Tom Rini
2009-01-12 20:30             ` Esben Haabendal
2009-01-09 17:04           ` Tom Rini
2009-01-12 20:47             ` Tom Rini
2009-01-10 15:33           ` Tom Rini
2009-01-10 19:06             ` Tom Rini
2009-01-14  1:15           ` Tom Rini
2009-01-14 23:17             ` Tom Rini
2009-01-17  2:54               ` Tom Rini
2009-01-17  4:47           ` Tom Rini
2009-01-22 18:10             ` Tom Rini
2009-01-28 19:49               ` Tom Rini
2009-01-01 22:15 ` Tom Rini
2009-01-01 23:19 ` Richard Purdie
2009-01-03 11:17   ` Richard Purdie
2009-01-02 12:58 ` Koen Kooi
2009-01-14  0:03 ` Robert Schuster [this message]

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=496D2BDB.6030603@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=rpurdie@rpsys.net \
    /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.