[
https://issues.apache.org/jira/browse/AVRO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039695#comment-13039695
]
Doug Cutting commented on AVRO-829:
-----------------------------------
This looks good. A few comments and questions about the patch:
- is it possible to have a single list of all languages, so that adding a new
language is less error-prone?
- it might be nice if the 'e' function accepted a list rather than a string as
the command, so that one could more easily pass commands that incorporate
quotes in their parameters.
- test_rpc_interop.sh might still run, restricted the lang provided. The
'clients' and 'servers' list there should be simply set to include only the
language specified.
> Enhance the build.sh script to support building a subset of the available
> language bindings
> -------------------------------------------------------------------------------------------
>
> Key: AVRO-829
> URL: https://issues.apache.org/jira/browse/AVRO-829
> Project: Avro
> Issue Type: Improvement
> Components: build
> Environment: POSIX compatible operating systems.
> Reporter: Joseph Koshy
> Attachments: option-l.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Avro supports a number of language bindings, currently: {{c}}, {{c++}},
> {{c#}}, {{java}}, {{ruby}}, {{php}}, {{python}}.
> The top level build script ({{build.sh}}) attempts to build all language
> bindings by default. Thus, building Avro from source requires compilers and
> interpreters for *all* these languages to be present on a developer's system.
> The attached patch adds support for a {{-l}} _LANG_ option to {{build.sh}},
> allowing the build to be restricted to the specified language(s). This
> feature allows someone interested in just a few bindings to build only the
> relevant parts of the Avro source tree.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
