On Fri, Feb 12, 2010 at 04:11:35PM +0100, Steffen Sledz wrote:
> Martin Jansa wrote:
> >> .../vala-dbus-binding-tool-native_git.bb | 10 ----------
> >> .../vala-dbus-binding-tool-native_git.bb | 10 ++++++++++
> >> 2 files changed, 10 insertions(+), 10 deletions(-)
> >> delete mode 100644
> >> recipes/freesmartphone/vala-dbus-binding-tool-native_git.bb
> >> create mode 100644
> >> recipes/vala-dbus-binding-tool/vala-dbus-binding-tool-native_git.bb
> >
> > Why not use that non-native package or at least that new .inc file or
> > ideally BBCLASSEXTENDS?
>
> Hmmm? I'm not really familiar with BBCLASSEXTENDS.
grep recipes for examples, but in short
if you add BBCLASSEXTENDS="native" in
vala-dbus-binding-tool_git.bb
it will be like having vala-dbus-binding-tool-native_git.bb with
include for non-native and inherit native (and will save few seconds for
parsing second file I guess)
> I believe sharing recipe stuff between non-native and native
> packages i could realize like in recipes/vala/. But i've
> no idea how to bring the numbered version we need (0.1.3)
> together with the git version the freesmartphone guys use.
If you insist on having versioned recipe (good), then please add both
0.1.3 and git recipe with BBCLASSEXTENDS.
You can share all metadata except SRC_URI and S, between versioned and git.
Or even better, put generic SRC_URI (with ${PV} and name=archive) and then
overwrite that only in git recipe. This way new version is created by just
cp pn_pv.bb pn_pvNew.bb and update checksums in pn_pvNew.bb.
> Anyone an example for this?
yes in recipes/* :)
--
uin:136542059 jid:[email protected]
Jansa Martin sip:[email protected]
JaMa
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
