You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2018/07/19 17:17:00 UTC

[jira] [Resolved] (ZOOKEEPER-3077) Build native C library outside of source directory

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

Patrick Hunt resolved ZOOKEEPER-3077.
-------------------------------------
    Resolution: Fixed

Issue resolved by pull request 557
[https://github.com/apache/zookeeper/pull/557]

> Build native C library outside of source directory
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-3077
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3077
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.5.4, 3.6.0, 3.4.13
>            Reporter: Kent R. Spillner
>            Assignee: Kent R. Spillner
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.5, 3.4.14
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Allow building native C library outside of source directory.  Everything works out-of-the-box with the existing autoconf infrastructure, except the location of the generated jute header & source is relative to the build directory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)