On Wed, Mar 16, 2011 at 08:28:39AM +0100, Frans Meulenbroeks wrote: > 2011/3/16 Khem Raj <[email protected]>: > > On 3/15/2011 11:22 PM, Ahsan, Noor wrote: > >> > >> Hello, > >> > >> I was looking at the libxml2 package. While going through the recipes I > >> came to know that its native package depends on python-native package as > >> well. This dependency is defined in libxml2.inc file. > >> > >> DEPENDS_virtclass-native = "python-native" > >> > >> This package build fine after removing this dependency. I am not clear > >> why this dependency is being added in libxml2 package. Can somebody > >> clear that to me. While looking at the git log I came to know that this > >> change is coming from libxml2-native.inc file. But I am not clear why > >> this dependency was added as this package build fine without it. > >> > >> Please help me in understanding this dependency. Thanks. > > > > Try to build this recipe from scratch and see if it still works then we can > > remove the dep
That's not enough, libxml2-native builds fine.. but then xml2po
will fail if there isn't libxml2-native built with python support.
see a25f07ca6159e1cd5b8a215ca5da8405fb1b9053
So yes.. for such tests you should build recipe from scratch _and_ check
if resulting package/sysroot is still the same.
Regards,
> I'm not sure if that is the right way.
> It might well be that typically python-native is already there in a
> scratch build because some earlier package needed it (or even because
> of the scheduling of build steps.
>
> Probably a better way is to build with packaged staging (with staging
> dir outside TMPDIR) then rm TMPDIR and bake the package.
> Alternately peek into the package to see if it needs python. If it is
> needed then the DEPENDS should stay.
>
> Looking at the issue at hand maybe the best person to ask is Martin
> Jansa as he last touched that line according to git blame:
> 3cd9ddbf recipes/libxml/libxml2.inc (Martin Jansa
> 2010-02-26 12:32:53 +0100 5) DEPENDS_virtclass-native =
> "python-native"
>
> The other thing is that further on in the .inc file I see:
> XPY_virtclass-native = " --with-python=${PYTHON_DIR}"
>
> This strongly suggests a hard dependency on python, so removing the
> DEPENDS "because it builds without it" does not seem to be a good plan
> to me.
>
> My strong feeling is that recipes should be self-contained (so should
> list all packages they need to build, minus the ones that are
> inherited from classes (and maybe a few implicit ones like maybe make)
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> [email protected]
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: [email protected]
pgpCDuVjisvQX.pgp
Description: PGP signature
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
