[oe] [PATCH] gawk-native_3.1.4.bb: Removed legacy style staging
Frans Meulenbroeks
fransmeulenbroeks at gmail.com
Thu Aug 19 11:13:58 UTC 2010
2010/8/19 Fahad <Fahad_Usman at mentor.com>:
>
> Hi Frans,
> With this do_install function, I get only one binary file
> (sysroots/i686-linux/usr/bin/gawk) in the resulting .ipk file, but if I
> remove the do_install function from the recipe and let the autotools's
> do_install execute, a bunch of other binary files end up in the .ipk
> file along with a lot of other stuff. Is it okay to have extra files in
> the ipk package or should I leave the do_install function in the recipe.
>
> Secondly, is there a way to merge native and non-native recipes if the
> native one need a different do_install function?
It is considered ok if do_install installs some additional files in
the native case.
(and maybe some will feel it is desirable that for native everything
is properly installed).
When merging native and nonnative:
if a different install is absolutely needed you can add a
do_install_virtclass-native
function
see e.g. the recipe for grep 2.6.3
you an also extend the recipe for native e.g. by
do_install_append_virtclass-native() {
do_install_prepend_virtclass-native() {
but (very odd) I have also seen a case with:
do_install_virtclass-native_prepend()
Note that virtclass-native only works with BBCLASSEXTEND = "native"
However note that having to redefine do_install (or modifying it) only
needs to be done very rarely. Currently we only have a handful of
recipes that do so, so generally it should not be needed
Frans
More information about the Openembedded-devel
mailing list