On Tue, May 24, 2011 at 10:48, Stefan Sperling <stsp_at_elego.de> wrote:
> On Tue, May 24, 2011 at 10:36:21AM -0400, Greg Stein wrote:
>> On Tue, May 24, 2011 at 09:39, Mark Phippard <markphip_at_gmail.com> wrote:
>> > Wasn't it JavaHL that failed to compile? If we want developers to
>> > always compile the Java bindings then why don't we remove it as a
>> > separate build target and just make it part of our default?
>> You're right. We should probably Just Do This.
>> We've gone back and forth on bindings for a long time now. I don't
>> really see much of a problem if we just built them by default (any
>> bindings that are configured for the local machine, that is).
>> Ten years ago? Yeah... compiles weren't exactly speedy. But today?
>> Pfft. Compile it all. :-)
>> Thoughts, people?
> No objections. I already have my build automated to do this.
> Except if you do this please provide a way to explicitly turn specific
> bindings off at configure time. E.g. JavaHL does *not* build with
> threadless APR and I really have no idea how to fix that, I've tried...
Looks like --with-jdk=no will disable the java bindings. I assume
there are similar for the other bindings.
I'll double-check before enabling the bindings build by default. (just
waiting for more feedback now)
Received on 2011-05-24 16:56:42 CEST