On Sat, Dec 28, 2019 at 3:29 AM Andreas Müller <[email protected]> wrote: > > On Sat, Dec 28, 2019 at 4:22 AM Khem Raj <[email protected]> wrote: > > > > On Fri, Dec 27, 2019 at 3:48 PM Andreas Müller <[email protected]> > > wrote: > > > > > > On Sat, Dec 28, 2019 at 12:19 AM Khem Raj <[email protected]> wrote: > > > > I think version specific information should be in bb file not inc > > > we have a native build and it just builds some tools required. Both > > > native/target share same version which is set in > > > evolution-data-server.inc. So maybe I missed something but what kind > > > of change do you suggest? > > > > > > > hmm if it shares with native/nativesdk that might be fine > > why dont we use bbclassextend for the native version ? > > > * Native and target recipes do not share much in common (see > evolution-data-server.inc): As said: Native recipe just builds few > necessary tools with a set of dependencies reduced to minimum. > * Most pieces would require a specific entry > (DEPENDS/do_configure/do_compile/do_install/RDEPENDS) for native and > target. Since target recipe is already more complex than most recipes, > extending to native would confuse more and cause recipe less readable. > * There is no nativesdk yet. If someone needs it: extending target > recipe should do. > * This discussion is unrelated to this patch - right? >
yes > Andreas -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
