avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiruvalluvan M. G. (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AVRO-1015) Support for C++ build using Micrsoft Visual Studio on Windows
Date Sat, 04 Feb 2012 14:37:53 GMT

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

Thiruvalluvan M. G. updated AVRO-1015:

    Attachment: AVRO-1015.patch

This patch enables building on native Windows (without Cygwin). Please see the MainPage.dox
for details.
Tested that it works on Ubuntu, RHEL 4.7, RHEL 5.4 and Cygwin as well.
> Support for C++ build using Micrsoft Visual Studio on Windows
> -------------------------------------------------------------
>                 Key: AVRO-1015
>                 URL: https://issues.apache.org/jira/browse/AVRO-1015
>             Project: Avro
>          Issue Type: Improvement
>          Components: c++
>         Environment: Windows
>            Reporter: Thiruvalluvan M. G.
>            Assignee: Thiruvalluvan M. G.
>             Fix For: 1.6.2
>         Attachments: AVRO-1015.patch
> At present, Avro C++ builds on Cygwin but does not build natively for Windows using Visual
Studio. The main stumbling block has been integration with Flex and Bison. Now that AVRO-956
removed dependence on Flex and Bison, we should start supporting Visual Studio Builds. A few
issues need to be addressed, which the forthcoming patch take care of:
> - signed to unsigned conversion and vice-versa should be explicit. Otherwise the compiler
generates warnings.
> - Floating point literals unless suffixed with f are considered double. The compiler
warns about loss of precision, even though the actual values don't really need double.
> - Taking &v[0] to obtain the pointer to the underlying array in a vector fails in
debug mode if the size of the vector is 0. Similar thing happens for strings as well.
> - If a function or a class is exposed outside a DLL, __dllexport should be specified
similarly if they are used outside the DLL, __dllimport should be specified.
> - min and max are both functions in Standard C++ library and macros in Windows standard
library, which causes conflict.
> - The Unix file handling does not work in Windows. It needs its own method.
> - Boost library and TR1 clash in a couple of places especially in "make_shared".

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


View raw message