[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH RFC v2] build: add autoconf to replace custom checks in tools/check

>>> On 10.01.12 at 14:32, Roger Pau MonnÃ<roger.pau@xxxxxxxxxxxxx> wrote:
> 2012/1/10 Jan Beulich <JBeulich@xxxxxxxx>:
>>>>> On 09.01.12 at 21:37, Roger Pau Monne <roger.pau@xxxxxxxxxxxxx> wrote:
>>> @@ -87,9 +88,21 @@ 2. cd to xen-unstable (or whatever you s
>>>  3. For the very first build, or if you want to destroy build trees,
>>>     perform the following steps:
>>> +   If you are building Xen from a repository (git or mercurial) you
>>> +   must run:
>>> +
>>> +    # ./autogen.sh
>>> +
>>> +   Before executing ./configure (this step can be ommited when
>>> +   building from a distribution package).
>>> +
>>> +    # ./configure
>> Can these two steps be automated (i.e. the need to run either
>> be determined by the absence of some file(s), and them being
>> invoked from the top level Makefile)?
> It probably could, just making a target for config.h in
> tools/Makefile. Are you sure this is what we want? The configure
> script has several build options that should be set by the user (or at
> least reviewed, so the user know it has build/install options).

Let's see what other want; my thinking is that if one didn't care to
run ./configure manually, default settings are intended. That's
what an invocation without arguments should result in, without
any user interaction.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.