[ https://issues.apache.org/jira/browse/AVRO-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802623#action_12802623 ]
Matt Massie commented on AVRO-349: ---------------------------------- Scott- bq. this will build the html documentation, and copies the documentation to build/doc/cpp. I think the proper location for documentation would be {{build/avro-doc-$VERSION/api/c++/}}. If you look at the top-level build.sh, you see that it does... {code} (cd doc; ant) (cd build; tar czf - avro-doc-$VERSION) > dist/avro-doc-$VERSION.tar.gz {code} ...on "dist" to create the avro-doc tarball. > 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 > Attachments: apply349.sh, 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.