Thanks,
I'll get a few systems to point to it and give it a stressing.
Carl.
Steve Huston wrote:
Hi Carl,
The Windows DLL-building stuff is in a useable form on the qpid-1673
branch in svn.
I've also built it on RHEL 5.
-Steve
-----Original Message-----
From: Carl Trieloff [mailto:[email protected]]
Sent: Sunday, March 01, 2009 9:21 PM
To: [email protected]
Cc: 'David Ingham'
Subject: Re: Request to get Windows DLL changes into M5
Sure, let's bang it a day or two on the branch, and then
merge. What is
the svn rev to bang on.
Carl.
Steve Huston wrote:
I'm working to integrate the C++ DLL changes originating
from Danushka
(QPID-1673) into M5. The situation at this point is that the
common
and client libs build as DLLs. The broker, which was built as one
giant exe in M4, is now split into a broker lib and qpidbroker
exe.
The broker lib is still building static lib, but at least can link
into the unit tests.
The work is on the qpid-1673 branch and I've also built on Linux.
Although the code changes are primarily added decorations
that Windows
requires to declare DLL exports, I'm not comfortable enough
with it to
drop it into trunk at this time, but that will early this week.
I'm
hoping that the Powers That Be will be amenable to my
committing this
on trunk then. Or, it could go on the M5 branch. Either
way, can I get
this in M5?
Thanks,
-Steve
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
