On 21.06.2011, at 09:57, Jan Kiszka wrote: > On 2011-06-21 09:46, Alexander Graf wrote: >> >> On 21.06.2011, at 09:27, Jan Kiszka wrote: >> >>> On 2011-06-21 09:26, Alexander Graf wrote: >>>> >>>> On 21.06.2011, at 09:23, Jan Kiszka wrote: >>>> >>>>> On 2011-06-21 09:21, Alexander Graf wrote: >>>>>> >>>>>> On 21.06.2011, at 08:26, Jan Kiszka wrote: >>>>>> >>>>>>> From: Jan Kiszka <jan.kis...@siemens.com> >>>>>>> >>>>>>> Introduce CONFIG_XEN_BACKEND so that this new config solely controls the >>>>>>> target-independent backend build and CONFIG_XEN can focus on per-target >>>>>>> building. >>>>>> >>>>>> What's the incentive here? I very much doubt we'll ever want to support >>>>>> xen on !x86. In fact, the better solution would probably be to just move >>>>>> every build component to x86 specific code. >>>>> >>>>> I doubt that as well. But keeping the backend centrals prevent building >>>>> them twice (for i386 and x86_64). >>>> >>>> How can we not build them twice without risking that target_ulong breaks >>>> somewhere along the way? >>> >>> Because the backends don't depend on that. And we already build them >>> only once, your your logs. :) >> >> So what does the patch change then if it's already only built once? > > It allows to clean up Makefile.target like I did as CONFIG_XEN is no > longer defined for all targets but only for those that actually support Xen.
Seems to make sense. Let's hope it doesn't break anything :) Alex
