Sure, it may take a while to get the proton group's approval for a merge. In the meantime, I have a snapshot of the Windows port at github.
protonWinSnap is a snapshot of the code and protonWin will be the one used to add patches for the proton community to check out. To see the Windows port running, use this branch https://github.com/MaryDHinton/qpid-proton/tree/protonWinSnap To compile and run this code, all you should need to do is: Select the zip button on the page above and extract the code. Select the proton.sln file in the proton-c folder and open it in Visual Studio 2010. Compile the qpid-proton and proton projects. Go to the Debug folder and run proton (the debug version is the only mode set up, the release will have to be set up). You should be able to see messages passed between a proton client and server. The patches will be added to this branch as they become available: https://github.com/MaryDHinton/qpid-proton/commits/protonWin Let me know how it works for you. Mary Hinton -----Original Message----- From: Ljupco Taseski [mailto:t...@digiverse.si] Sent: Friday, November 30, 2012 5:45 AM To: proton@qpid.apache.org Cc: m.hin...@nc.rr.com Subject: Re: Proton Port for Windows Is it possible to have a look at the Windows port? I wouldn't mind even if it is a simple tgz/zip snapshot. Thanks, Ljupco On 14 November 2012 15:19, Mary Hinton <m.hin...@nc.rr.com> wrote: > Hi everyone, > > > > I'd like to share the status of the Windows port of the proton code. > > > > The last rebase of the proton dll codebase was this Saturday, Nov. 10th. > > > > I haven't updated to the latest python tests yet, but currently, the > port is running and passing most of the python tests. > > Totals: 119 tests, 105 passed, 6 skipped, 0 ignored, 8 failed > > > > I can run proton in both client and server mode and pass the messages > between the client/server proton executables. > > > > It will be a while for all the Jiras for the port to be discussed and > implemented to merge the two ports. I tried to maintain the code to > keep the two versions working, but haven't actually tested my version > on Linux yet. > There are #ifdef's around areas that are specific to each port. A lot > of these #ifdef's can be merged when the proton group decides on the > best way to handle the specific areas. > > > > In the meantime, I would like to have a public place to put the port > so that others can join in with the Windows version. > > What is the best way to do this using git so that I don't interfere > with the current codebase? > > > > Thanks, > > Mary Hinton > >
