I believe this is the actual solution I am using, the tasks are always executed but my install steps differ and only install the appropriate file, which in turn I believe generate appropriate packages. That works too, but I do not want to get into issues where the build on the target fails due to arch issue and having to pull unnecessary dependency packages on my target and lost cpu cycle. But it would still work, which is why I am using it but looking for an alternative. Yannick Koehler
De : Burton, Ross [mailto:[email protected]] Envoyé : March-13-15 7:51 AM À : Koehler, Yannick (HP Networking) Cc : Paul Eggleton; [email protected] Objet : Re: [yocto] running task only for native but not target? On 13 March 2015 at 11:46, Koehler, Yannick (HP Networking) <[email protected]> wrote: Thanks, yes that is likely to work, I will try it. I was looking for a more Yocto-like solution using the overriding stuff but it seems the overriding doesn't apply in this particular situation. An alternative solution would be to build everything all the time, and package correctly so that you don't install unrequired binaries on the target. Ross -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
