Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Sun, 9 Oct 2011 08:24:29 +0000 (UTC)
From: "Thiruvalluvan M. G. (Updated) (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: 
 <1336117267.12493.1318148669660.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <98772139.771.1317847949730.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AVRO-908) Add an option to build avrocpp as a
 static library
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thiruvalluvan M. G. updated AVRO-908:
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0
           Status: Resolved  (was: Patch Available)

Committed revision 1180563.

Thank you Nebojsa.

It now builds both static and shared libraries. For linking with static library the user needs to give {{- lavrocpp_s}} instead of {{- lavrocpp}}. In addition the user may have to give one or more of {{- lboost_regex}}, {{- lboost_filesystem}} and {{- lboost_system}} depending on which parts of Avro library is used.
                
> Add an option to build avrocpp as a static library
> --------------------------------------------------
>
>                 Key: AVRO-908
>                 URL: https://issues.apache.org/jira/browse/AVRO-908
>             Project: Avro
>          Issue Type: New Feature
>          Components: c++
>    Affects Versions: 1.5.4
>            Reporter: Nebojsa Sabovic
>            Assignee: Nebojsa Sabovic
>              Labels: cmake
>             Fix For: 1.6.0
>
>         Attachments: AVRO-908-rev-2.patch, AVRO-908.patch
>
>
> Use BUILD_SHARED_LIBS variable to control whether Avro-c++ library is built as a shared library or as a static library. That way, people who want static library can use 'cmake -DBUILD_SHARED_LIBS=OFF'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira