On 05/03/2012 05:39 AM, Koen Kooi wrote:
>
> Op 3 mei 2012, om 10:47 heeft Richard Purdie het volgende geschreven:
>
>>
>> The point of these is to trigger them to build whenever a qemu image is
>> built. This makes a lot of sense in some use cases, it also does not
>> make sense in some other cases and it is not possible for the system to
>> mind read and tell the difference.
>
> What about having the runqemu* scripts call bitbake to build the -native
> helpers when they are missing?
>
Clearly this works from the usability angle of keeping a minimal number of
steps, but there are two side effects because it is implemented as a "if helper
binary exists ; then bitbake ...".
1) Everything you need to get started was not really there after completing the
build
2) If the qemu helpers are updated they will not get rebuilt when you run your
typical rebuild
*** NOTE I realize that this probably does not happen too often, but it is
a possibility
I would certainly not want bitbake to run each time you invoke runqemu to check
if it is updated because that unnecessarily delays the start of the simulator.
It would seem to me the best approach is to use Richard's idea so as to allow
folks to not build the helpers if someone really doesn't want them, as well as
have runqemu auto build the helpers if they are not there so as to keep the use
cases simple.
Respectfully,
Jason.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
