You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Laurent Moss (JIRA)" <ji...@apache.org> on 2012/07/22 20:15:33 UTC

[jira] [Created] (AVRO-1133) Build failing with Visual Studio C++ 2008 due to missing stdint.h

Laurent Moss created AVRO-1133:
----------------------------------

             Summary: Build failing with Visual Studio C++ 2008 due to missing stdint.h
                 Key: AVRO-1133
                 URL: https://issues.apache.org/jira/browse/AVRO-1133
             Project: Avro
          Issue Type: Bug
          Components: c++
    Affects Versions: 1.7.1
         Environment: Windows XP Professional 32-bit SP3, Microsoft Visual Studio 2008 SP1
            Reporter: Laurent Moss


Several Avro C++ API files refer to stdint.h. However, this file is not available on Microsoft Visual Studio 2008 (and previous versions). This results in several build errors such as:
C:\workspace\avro-cpp\api\Validator.hh(24) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory

This is similar to an issue previously faced by the Avro C API:
https://issues.apache.org/jira/browse/AVRO-551

This was issue was fixed in the Avro C API by integrating open-source ISO C9x compliant stdint.h and inttypes.h files for Microsoft Visual Studio:
https://code.google.com/p/msinttypes/

An alternative for the Avro C++ API would be to replace references to stdint.h by references to Boost's cstdint.hpp
http://www.boost.org/doc/libs/1_50_0/boost/cstdint.hpp




--
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

        

[jira] [Commented] (AVRO-1133) Build failing with Visual Studio C++ 2008 due to missing stdint.h

Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421132#comment-13421132 ] 

Thiruvalluvan M. G. commented on AVRO-1133:
-------------------------------------------

We have to make a tradeoff here. The boost solution is better because we already depend on boost and no new dependency gets added. But all references to int8_t etc should now become boost::int8_t, which doesn't look nice.

On the other hand, the changes are minimal with msinttypes, but we need to copy the code from google code.

My preference is for the latter.

Is it possible for you submit a patch after verifying that it works with VS 2008?


                
> Build failing with Visual Studio C++ 2008 due to missing stdint.h
> -----------------------------------------------------------------
>
>                 Key: AVRO-1133
>                 URL: https://issues.apache.org/jira/browse/AVRO-1133
>             Project: Avro
>          Issue Type: Bug
>          Components: c++
>    Affects Versions: 1.7.1
>         Environment: Windows XP Professional 32-bit SP3, Microsoft Visual Studio 2008 SP1
>            Reporter: Laurent Moss
>
> Several Avro C++ API files refer to stdint.h. However, this file is not available on Microsoft Visual Studio 2008 (and previous versions). This results in several build errors such as:
> C:\workspace\avro-cpp\api\Validator.hh(24) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory
> This is similar to an issue previously faced by the Avro C API:
> https://issues.apache.org/jira/browse/AVRO-551
> This was issue was fixed in the Avro C API by integrating open-source ISO C9x compliant stdint.h and inttypes.h files for Microsoft Visual Studio:
> https://code.google.com/p/msinttypes/
> An alternative for the Avro C++ API would be to replace references to stdint.h by references to Boost's cstdint.hpp
> http://www.boost.org/doc/libs/1_50_0/boost/cstdint.hpp

--
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