[
https://issues.apache.org/jira/browse/COUCHDB-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921028#action_12921028
]
Paul Joseph Davis commented on COUCHDB-919:
-------------------------------------------
I'm not sure what this would accomplish. The basic progression for adding
configure settings is when a large group of people fails to build CouchDB
properly due to a weirdness with a dependency.
For instance, the JS config options are needed because Spidermonkey's
distribution is so haphazard it can be in about five different places, and
that's just counting the places where major vendors install it. Erlang is
always kind of a weirdo because we're adding an include search path to
something like $ERL_PREFIX/lib/erlang/include. And the openssl bin dir is
special Windows-fu that I have no knowledge of.
For the proposed options i'm not even sure what they would set. The include
search path? Or the linker search path maybe? Or both by appending include/ and
lib/? Also, I've not heard of any consistent problems faced by users building
couchdb related to these three dependencies.
All in all, my initial reaction is that if a user is advanced enough to attempt
to build with dependencies in non-standard locations, then they should be
advanced enough to handle using the available environment variables to control
the build, especially when actually running a CouchDB built like this is going
to more than likely require fancy environment customization.
> Add build options
> -----------------
>
> Key: COUCHDB-919
> URL: https://issues.apache.org/jira/browse/COUCHDB-919
> Project: CouchDB
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 1.0.1
> Environment: *.nix, OS X
> Reporter: Tracy Flynn
> Priority: Minor
>
> Add some build options to support non-default organization of CouchDB
> dependencies.
> If /usr/local is taken as an example for the default installation directory
> (prefix) for CouchDB, then the installation works without modification only
> if other dependencies are configured and built with the same prefix.
> Some options allow the changing of the location of the dependency - e.g.
> --with-js-lib for Spidermonkey
> The standard set appears to be:
> --with-erlang=PATH set PATH to the Erlang include directory
> --with-js-include=PATH set PATH to the SpiderMonkey include directory
> --with-js-lib=PATH set PATH to the SpiderMonkey library directory
> --with-openssl-bin-dir=PATH path to the open ssl binaries for distribution
> on Windows
> A suggestion for others that would help with dependencies in non-standard
> location:
> --with-openssl-dir - for the general OpenSSL case
> --with-icu-dir=<xxx> (might need a greater number of options - I'm not
> familiar with the full feature set for ICU)
> --with-curl-dir=<xxx>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
