[
https://issues.apache.org/jira/browse/AVRO-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965477#action_12965477
]
Scott Banachowski commented on AVRO-700:
----------------------------------------
Regarding the use of flex and bison, since these generate C files, we could
probably just check in the generated files... then on platforms without
flex/bison, they can build without needing to regenerate them. Only people who
need to modify the lexer code need to run flex/bison.
The python script is a code generator to build the serialization code from a
schema, and it's not strictly needed to build the library. It's used in unit
tests since the output code exercises a lot of the functionality.
> Change C++ build system to C++
> ------------------------------
>
> Key: AVRO-700
> URL: https://issues.apache.org/jira/browse/AVRO-700
> Project: Avro
> Issue Type: Improvement
> Components: c++
> Affects Versions: 1.5.0
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.5.0
>
> Attachments: apply-patch.sh, AVRO-700.patch
>
>
> If we move from the current automake to CMake, build becomes portable across
> multiple platforms. Prior to this patch, Avro C++ was building on Cygwin but
> was crashing. I've tested this on Ubuntu 10.04 and Cygwin.
> There are problems making it work with Visual Studio 2008 Express, not
> because of CMake, but because the current build procedure needs Flex, Bison
> and python. Visual Studio seems to have trouble with these three.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.