You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by Andrew Stitcher <as...@redhat.com> on 2012/12/05 23:04:11 UTC
Some proton portability work.
I've committed some portability work on proton today.
At this point, proton should configure and compile without error on
FreeBSD and MacOS X.
I've also done a bit of work which improves compilation under gcc on
Solaris too, but this isn't finished (Solaris is missing any
functionality to easily ignore SIGPIPE when writing to closed sockets).
I've also done a bit of work to get it cross compile under mingw32, but
again there are some remaining issues (ignoring the fact that the driver
code for Windows isn't finished anyway)
Questions, bugs etc. to me
Andrew
Re: Some proton portability work.
Posted by "Weston M. Price" <wp...@redhat.com>.
+1
Good stuff all around.
On Dec 5, 2012, at 5:27 PM, William Henry <wh...@redhat.com> wrote:
> Excellent work Andrew.
>
> William
>
>
> On Dec 5, 2012, at 5:04 PM, Andrew Stitcher <as...@redhat.com> wrote:
>
>> I've committed some portability work on proton today.
>>
>> At this point, proton should configure and compile without error on
>> FreeBSD and MacOS X.
>>
>> I've also done a bit of work which improves compilation under gcc on
>> Solaris too, but this isn't finished (Solaris is missing any
>> functionality to easily ignore SIGPIPE when writing to closed sockets).
>>
>> I've also done a bit of work to get it cross compile under mingw32, but
>> again there are some remaining issues (ignoring the fact that the driver
>> code for Windows isn't finished anyway)
>>
>> Questions, bugs etc. to me
>>
>> Andrew
>>
>>
Re: Some proton portability work.
Posted by William Henry <wh...@redhat.com>.
Excellent work Andrew.
William
On Dec 5, 2012, at 5:04 PM, Andrew Stitcher <as...@redhat.com> wrote:
> I've committed some portability work on proton today.
>
> At this point, proton should configure and compile without error on
> FreeBSD and MacOS X.
>
> I've also done a bit of work which improves compilation under gcc on
> Solaris too, but this isn't finished (Solaris is missing any
> functionality to easily ignore SIGPIPE when writing to closed sockets).
>
> I've also done a bit of work to get it cross compile under mingw32, but
> again there are some remaining issues (ignoring the fact that the driver
> code for Windows isn't finished anyway)
>
> Questions, bugs etc. to me
>
> Andrew
>
>
Re: Some proton portability work.
Posted by "Weston M. Price" <wp...@redhat.com>.
Looks good on OSX 10.8.2
Compilation is fine, send/recv work fine as well.
-W
On Dec 5, 2012, at 5:04 PM, Andrew Stitcher <as...@redhat.com> wrote:
> I've committed some portability work on proton today.
>
> At this point, proton should configure and compile without error on
> FreeBSD and MacOS X.
>
> I've also done a bit of work which improves compilation under gcc on
> Solaris too, but this isn't finished (Solaris is missing any
> functionality to easily ignore SIGPIPE when writing to closed sockets).
>
> I've also done a bit of work to get it cross compile under mingw32, but
> again there are some remaining issues (ignoring the fact that the driver
> code for Windows isn't finished anyway)
>
> Questions, bugs etc. to me
>
> Andrew
>
>
RE: Some proton portability work.
Posted by Mary Hinton <m....@nc.rr.com>.
That sounds good.
-----Original Message-----
From: Cliff Jansen [mailto:cliffjansen@gmail.com]
Sent: Wednesday, December 05, 2012 6:33 PM
To: proton@qpid.apache.org
Subject: Re: Some proton portability work.
Hi Mary,
Unless you have a problem with the driver in
https://reviews.apache.org/r/6302/
I was just about to dust that off (update it and/or pull in your github
work) and work it in parallel with proton-159. In theory the 2 together
should result in proton working with C++ and Windows libraries. The
additional steps to get a Visual Studio implementation should be very
straight forward after that.
As before, the intent is to get a functional driver (without ssl for
now) that can get people going on Windows. A high performance driver (with
overlapped io presumably) and with ssl integration would follow later.
Cliff
On Wed, Dec 5, 2012 at 2:45 PM, Mary Hinton <m....@nc.rr.com> wrote:
> What is planned for the driver code for Windows?
> Maybe I could help.
> I have a Windows port running and could put more patches in Jira for
changes to the driver code required by Windows.
> Thanks,
> Mary Hinton
>
>
> -----Original Message-----
> From: Andrew Stitcher [mailto:astitcher@redhat.com]
> Sent: Wednesday, December 05, 2012 5:04 PM
> To: proton
> Subject: Some proton portability work.
>
> I've committed some portability work on proton today.
>
> At this point, proton should configure and compile without error on
FreeBSD and MacOS X.
>
> I've also done a bit of work which improves compilation under gcc on
Solaris too, but this isn't finished (Solaris is missing any functionality
to easily ignore SIGPIPE when writing to closed sockets).
>
> I've also done a bit of work to get it cross compile under mingw32,
> but again there are some remaining issues (ignoring the fact that the
> driver code for Windows isn't finished anyway)
>
> Questions, bugs etc. to me
>
> Andrew
>
>
>
>
Re: Some proton portability work.
Posted by Cliff Jansen <cl...@gmail.com>.
Hi Mary,
Unless you have a problem with the driver in
https://reviews.apache.org/r/6302/
I was just about to dust that off (update it and/or pull in your
github work) and work it in parallel with proton-159. In theory the 2
together should result in proton working with C++ and Windows
libraries. The additional steps to get a Visual Studio implementation
should be very straight forward after that.
As before, the intent is to get a functional driver (without ssl for
now) that can get people going on Windows. A high performance driver
(with overlapped io presumably) and with ssl integration would follow
later.
Cliff
On Wed, Dec 5, 2012 at 2:45 PM, Mary Hinton <m....@nc.rr.com> wrote:
> What is planned for the driver code for Windows?
> Maybe I could help.
> I have a Windows port running and could put more patches in Jira for changes to the driver code required by Windows.
> Thanks,
> Mary Hinton
>
>
> -----Original Message-----
> From: Andrew Stitcher [mailto:astitcher@redhat.com]
> Sent: Wednesday, December 05, 2012 5:04 PM
> To: proton
> Subject: Some proton portability work.
>
> I've committed some portability work on proton today.
>
> At this point, proton should configure and compile without error on FreeBSD and MacOS X.
>
> I've also done a bit of work which improves compilation under gcc on Solaris too, but this isn't finished (Solaris is missing any functionality to easily ignore SIGPIPE when writing to closed sockets).
>
> I've also done a bit of work to get it cross compile under mingw32, but again there are some remaining issues (ignoring the fact that the driver code for Windows isn't finished anyway)
>
> Questions, bugs etc. to me
>
> Andrew
>
>
>
>
RE: Some proton portability work.
Posted by Mary Hinton <m....@nc.rr.com>.
What is planned for the driver code for Windows?
Maybe I could help.
I have a Windows port running and could put more patches in Jira for changes to the driver code required by Windows.
Thanks,
Mary Hinton
-----Original Message-----
From: Andrew Stitcher [mailto:astitcher@redhat.com]
Sent: Wednesday, December 05, 2012 5:04 PM
To: proton
Subject: Some proton portability work.
I've committed some portability work on proton today.
At this point, proton should configure and compile without error on FreeBSD and MacOS X.
I've also done a bit of work which improves compilation under gcc on Solaris too, but this isn't finished (Solaris is missing any functionality to easily ignore SIGPIPE when writing to closed sockets).
I've also done a bit of work to get it cross compile under mingw32, but again there are some remaining issues (ignoring the fact that the driver code for Windows isn't finished anyway)
Questions, bugs etc. to me
Andrew