Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <516477527.317651266356247936.JavaMail.jira@brutus.apache.org>
Date: Tue, 16 Feb 2010 21:37:27 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Updated: (AVRO-349) Make C++ builds work post AVRO-163
In-Reply-To: <322636770.322971263859014643.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting updated AVRO-349:
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.0
         Assignee: Scott Banachowski
           Status: Resolved  (was: Patch Available)

> Make C++ builds work post AVRO-163
> ----------------------------------
>
>                 Key: AVRO-349
>                 URL: https://issues.apache.org/jira/browse/AVRO-349
>             Project: Avro
>          Issue Type: Improvement
>            Reporter: Scott Banachowski
>            Assignee: Scott Banachowski
>             Fix For: 1.3.0
>
>         Attachments: apply349.sh, AVRO-349.patch, AVRO-349.patch
>
>
> This makes the c++ builds work with the top-level build by doing the the following:
> for build.sh test:
> this will build the c++ code and run its unit tests (all build artifacts are written in to build/c++/ )
> for build.sh dist:
> this will build the html documentation, and copies the documentation to build/doc/cpp.
> it also builds a dist tarball that contains  the c++ code, and copies it to dist/avro-cpp-$version.tgz
> for build.sh clean:
> this removes build/c++
> Is this in-line with what is expected after AVRO-163?  Please let me know if there are some things I overlooked.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.