On Sat, Aug 14, 2010 at 1:41 AM, Frans Meulenbroeks <[email protected]> wrote: > 2010/8/13 Koen Kooi <[email protected]>: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 13-08-10 14:25, Frans Meulenbroeks wrote: >>> 2010/8/13 Paul Menzel <[email protected]>: >>>> Am Freitag, den 13.08.2010, 17:17 +0600 schrieb [email protected]: >> >>>>> +NATIVE_INSTALL_WORKS = "1" >>>> >>>> I am really a noob, but is not that for “normal”, i.e. no *-native, >>>> recipes indicating no explicit native recipe is needed? >>> >>> Afaik this is not needed. >> >> If your -native recipe has something different than 'make install' in >> do_install, it needs NATIVE_INSTALL_WORKS = "1" but only if you use >> BBCLASSEXTEND to make it native. >> > The BBCLASSEXTEND part does not matter. > > If you have a -native recipe that does not use autotools and does not > use make install > NATIVE_INSTALL_WORKS = "1" > is needed. Without it the following code is generated: > > do_stage_native() { > # If autotools is active, use the autotools staging function, else > # use our "make install" equivalent > if [ "${AUTOTOOLS_NATIVE_STAGE_INSTALL}" == "1" ] > then > autotools_stage_all > else > oe_runmake install > fi > > } > > BTW this is a recipe that has no target equivalent so there is no > non-native variant.
if you have staging function which is not one of use_do_install_for_stage() or autotools_stage_all() or do_stage_native() and AUTOTOOLS_NATIVE_STAGE_INSTALL is 1 then legacy staging will be used. in such cases NATIVE_INSTALL_WORKS is used to indicate that whatever install function we have is good for staging so dont do legacy staging. > > Frans > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
