On 05/01/2012 08:19 PM, Peter Stuge wrote:
> Uri Lublin wrote:
>> For example usefull when running autogen.sh in src-dir and
>> running configure in a (different) build-dir.
>> ---
>> autogen.sh | 4 +++-
>> 1 files changed, 3 insertions(+), 1 deletions(-)
>>
>> diff --git a/autogen.sh b/autogen.sh
>> index 782bec7..2a05191 100755
>> --- a/autogen.sh
>> +++ b/autogen.sh
>> @@ -15,4 +15,6 @@ aclocal || exit 1
>> autoheader || exit 1
>> autoconf || exit 1
>> automake -a -c || exit 1
>> -./configure --enable-maintainer-mode --enable-examples-build $*
>> +if [ -z "$NOCONFIGURE" ]; then
>> + ./configure --enable-maintainer-mode --enable-examples-build $*
>> +fi
> Is NOCONFIGURE a widely established convention?
I've seen it in spice and some glib/gnome projects.
> It has been discussed to remove the configure call completely from
> autogen.sh, which I think might be a good idea.
I know some people like autogen.sh running configure.
Personally I prefer to run them separately, especially when I build
the project in a different build-dir.
With NOCONFIGURE the default stays the same, and all I need
to do is to define one more environment variable.
> Also, how do you feel about autoreconf -i ?
With new enough autoreconf I'm for it (-if)
Regards,
Uri.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
