On Tue, Jul 20, 2010 at 8:52 AM, Michael Smith <msm...@cbnco.com> wrote:
> Tom Rini wrote: > >> It's also needed, in some cases, to lock down your changes via OVERRIDES >> that will only match what you want to work on. For example, we're using a >> snapshot with an older python, so amend.inc in our python directory looks >> like: >> >> SRC_URI_append_pn-python-native = >> "file://python-2.6-r73342.patch;patch=1;pnum=0" >> PARALLEL_MAKE_pn-python-native = "" >> PR_append_pn-python-native .= ".1" >> >> So that we only change python-native and not all of the other python >> recipes. >> > > I think you could get the same effect by putting your amend.inc in a > python-native subdirectory under your overlay recipes/python directory. > > Maybe there's some native magic going on that would break that. (I've never > amended a -native package but I use the same trick for other recipes where > there are multiple .bb files are in the same OE directory.) Well, that works for -native or -cross, but there's no -target, so you have to use a pn- override to modify the target recipe but *not* native and cross. If you put it in python/, it applies to all of them. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel