You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Paul Joseph Davis (JIRA)" <ji...@apache.org> on 2011/04/17 18:33:05 UTC

[jira] [Updated] (COUCHDB-162) improve configure script's ability to find erl_driver.h

     [ https://issues.apache.org/jira/browse/COUCHDB-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis updated COUCHDB-162:
--------------------------------------

    Attachment: 0001-Automatically-detect-erl_driver.h-location.patch

This automatically pulls the Erlang include directory using the same logic as Rebar does. Basically just runs a couple Erlang commands and then patches together the directory structure.

Windows support is not included.

> improve configure script's ability to find erl_driver.h
> -------------------------------------------------------
>
>                 Key: COUCHDB-162
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-162
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Adam Kocoloski
>            Assignee: Noah Slater
>            Priority: Minor
>         Attachments: 0001-Automatically-detect-erl_driver.h-location.patch
>
>
> Hi, if I configure and install Erlang with a custom --prefix=/path/to/erlang, CouchDB's configure script finds `erl` and `erlc` from the environment, but it usually needs to be told about the location or erl_driver.h:
> ./configure --with-erlang=/path/to/erlang/lib/erlang/usr/include
> It'd be nice if the configure script could check that location automatically, e.g. determining /path/to/erlang by stripping bin/erl off the path to `erl` that it found earlier.  
> Alternatively, I think --with-erlang ought to be modified to take the path to the base of the Erlang installation, rather than the exact path to the location of the folder containing erl_driver.h.  Best,
> Adam

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira