>>> On 14.01.15 at 19:39, <konrad.w...@oracle.com> wrote: > On Wed, Jan 14, 2015 at 09:06:37AM +0000, Jan Beulich wrote: >> >>> On 13.01.15 at 21:43, <dgde...@tycho.nsa.gov> wrote: >> > On 01/13/2015 02:27 PM, Konrad Rzeszutek Wilk wrote: >> >> I was wondering if there would be any plans for configure.ac >> >> (or the m4 scripts) to have an --enable-xsm which would set >> >> XSM_ENABLE (or FLASK_ENABLE) to true? >> >> >> >> Right now by default to build with XSM one has to manually change >> >> the Config.mk ENABLE_XSM option to 'y'. >> > >> > Is the hypervisor build allowed to depend on having run ./configure >> > now? I think this was the reason why config.mk is being used. >> >> Correct - configury only controls the tools (and stubdom iirc). > > Ah that is right. Should we expand on that then? Make the hypervisor > build with different configure options?
I'd really try to avoid that; if any configuration should be needed, it should rather follow e.g. the Linux kernel model than the user space one used for the tools. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel