Nice-to-have fix for autogen.sh
Segher Boessenkool
segher at kernel.crashing.org
Wed Feb 1 11:51:16 EST 2012
> Again, it's not a matter of annoyances.
"Again"? You brought it up yourself! :-)
<snip>
> In the same vein, having samples built by default is probably also
> a must have for anybody getting started with a new project, as they
> might then be able to play with it immediately. On the other hand,
> this could (and probably should) be turned on by default in
> configure.ac, as it doesn't really impact release users, especially
> as we have very few samples to build.
It is also not helpful that our samples are built with the in-tree
built library, it doesn't give any example how to use the library
that way.
>> Why only for developers though?
>>
>> Run-time configurable logging sure would help :-)
>
> Not sure I understand your point there, since I went the extra mile
> to provide just that for all the people who use either my binaries
> or code from my branch, and as I stated, once we have the feature
> in in official, the importance of having logging on by default in
> autogen is greatly reduced.
What I am saying is that any user should be able to turn on logging
with any built version of libusbx, just like there should be seat
belts in any car, not just those used by the crash test dummies.
I think your patches give us the good stuff here?
>>>> If you're building a lot, you probably should run some ./build
>>>> anyway ;-)
>>>
>>> Why should I, when the default autogen.sh is just fine?
>>
>> Most people at least want a --prefix if they build a lot (since
>> they typically have many versions installed).
>
> Which they can provide to autogen.sh.
And?
My point is that people who build a lot just do not matter, they
_will_ have their own build scripts. Unless they really like
typing :-)
Segher
More information about the libusbx
mailing list