Hi Yves,

On 2012.07.23 10:42, Yves Arrouye wrote:
> I was a bit surprised that the default installation obtained by cloning
> (using git clone on the command
> line) git://github.com/libusbx/libusbx.git
> <http://github.com/libusbx/libusbx.git> did not include a configure or
> any of the artifacts generated by the autoconf suite.

This is intended. Be mindful that the git repository is primarily aimed 
at libusbx development and not distribution. The tarballs we provide for 
each release do include configure.

Also note that what we're doing isn't libusbx specific. Many projects 
are set this way as well.

> Using a fresh cloned directory and having MacPort's autoconf and friends
> first in my path (/opt/local/bin; those are later versions than
> Apple's), I had to do the following (from the top level directory):

Instead, you should have invoked one of ./bootstrap.sh or ./autogen.sh, 
to do this for you. Again, these are fairly common invocation steps for 
autotools based projects.

We are also documenting this step on the wiki 
(https://github.com/libusbx/libusbx/wiki#wiki-Accessing_the_Source):

"Also note that, when compiling from git, you may have to run 
./autogen.sh or run the autotools creation utilities, in order to have 
configure and Makefile created for you."

> Is that expected? If so, shouldn't the INSTALL file mentions that rather
> than say that one should simply have to run configure?

The INSTALL file is aimed at the distribution tarball, that already 
comes with a configure file. I'm not sure we should mention git specific 
steps there, as it may confuse tarball users.

If you think it's important, we can create a specific readme for git 
users, to mention the need to run one of the scripts, and that wouldn't 
be included in the tarball.

Regards,

/Pete



------------------------------------------------------------------------------
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

Reply via email to