You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Alan Conway <ac...@redhat.com> on 2016/07/05 23:55:55 UTC
Need windows porting help: proton and libuv have competing ssize_t
definitions.
I'm working on a libuv integration for proton (https://github.com/alanc
onway/qpid-proton/tree/c-engine) and on windows I ran into this
problem:
�D:\Users\aconway\proton\examples\c\libuv\simple_send.c
� simple_send.c
c:\program files\libuv\include\uv-win.h(27): error C2371: 'ssize_t' : redefinition; different basic types [D:\Users\aconway\proton\build\examples\c\libuv\libuv-simple_send.vcxproj]
����������D:\Users\aconway\proton\proton-c\include\proton/type_compat.h(118) : see declaration of 'ssize_t'
Now this hurts pretty badly. Both proton and libuv have macros I can
set to stop them from defining their version of ssize_t but if they
really are ending up as differently sized integer types then I can't
safely use either definition for both proton and libuv calls, and I
don't see any way to force the definitions to have different names
(it's a typedef not a macro)
Any thoughts?
Cheers,
Alan.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
[cancel] Re: Need windows porting help: proton and libuv have
competing ssize_t definitions.
Posted by Alan Conway <ac...@redhat.com>.
My dumb mistake, mixing 64 and 32 bit code.
On Tue, 2016-07-05 at 19:55 -0400, Alan Conway wrote:
> I'm working on a libuv integration for proton (https://github.com/ala
> nc
> onway/qpid-proton/tree/c-engine) and on windows I ran into this
> problem:
>
> �D:\Users\aconway\proton\examples\c\libuv\simple_send.c
> � simple_send.c
> c:\program files\libuv\include\uv-win.h(27): error C2371: 'ssize_t' :
> redefinition; different basic types
> [D:\Users\aconway\proton\build\examples\c\libuv\libuv-
> simple_send.vcxproj]
> ����������D:\Users\aconway\proton\proton-
> c\include\proton/type_compat.h(118) : see declaration of 'ssize_t'
>
> Now this hurts pretty badly. Both proton and libuv have macros I can
> set to stop them from defining their version of ssize_t but if they
> really are ending up as differently sized integer types then I can't
> safely use either definition for both proton and libuv calls, and I
> don't see any way to force the definitions to have different names
> (it's a typedef not a macro)
>
> Any thoughts?
>
> Cheers,
> Alan.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org