2009/3/11 Steve Huston <[email protected]>: > Hi Martin, > > FYI, part of the work Microsoft is funding me to do is produce a > prebuilt binary installer for M5. Where it will be offered from is not > yet determined, but it can always be from riverace.com. > > -Steve
Steve, That's great. What will the installer contain? Only Broker, Broker+Client or two installers one for each? Cheers >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Martin Ritchie >> Sent: Wednesday, March 11, 2009 7:07 AM >> To: [email protected] >> Subject: Re: [Discussion] Release Artefacts >> >> >> Thanks for everyone's input on this: >> >> Seems like we are all agreeing that more discreet packages >> would be better. >> >> Just to summerise what everyone has said I believe these packages is >> what everyone is looking for: >> >> A single source package for the source release as well as the cpp >> source package that removes the build dependency on ruby. The > provided >> binaries would be split in to broker, client, examples and tools. > The >> C++ binaries that we actually build could be limited to Windows, as >> downstream packagers will provide other builds we can link to. Each >> client language should have their own package and an additional >> example/documentation package. Finally we will have a set of > packages >> for the management tools from all languages. Carl, you mentioned > other >> C++ tools but on the wiki I only see details about QMF and QMan if > you >> let me know what the other items that we should package are I'll pop >> them on the list here: >> >> - Single Source package >> - C++ Source package >> - Binary Packages for >> + Brokers >> + C++ >> - Windows only from Qpid, simply link to other downstream > binary >> builds for other platforms >> + Java >> + Client and Example Package >> + C++ >> - Windows only from Qpid, simply link to other downstream > binary >> builds for other platforms >> + C# (0-8,0-10) >> + Java >> + Python >> + Ruby >> + Management >> - Eclipse JMX Console >> + Win >> + Linux >> + OS X >> - JMX Command Line Tool >> - QMan / WsDmAdapter >> >> >> Cheers >> >> Martin >> >> 2009/2/19 Steve Huston <[email protected]>: >> >> -----Original Message----- >> >> From: Rajith Attapattu [mailto:[email protected]] >> >> ... >> >> Binary distributions >> >> ------------------------------------ >> >> +1 on having separate builds for brokers, clients and management >> > tools >> >> when ever it makes sense. >> >> I have been advocating this for a while now. >> >> >> >> How ever as Aidan points out, for c++ its best we restrict our >> > selves >> >> to providing binaries for windows only. >> > >> > I have funding to produce Windows installer in the M5 (or whatever >> > it's called) timeframe. The contents and shape of that are >> not yet in >> > place, so I'm open to hearing what people think it should contain. >> > I've been working under the assumption that it will have: >> > >> > - broker binary >> > - built DLLs (broker, client, common) >> > - qmfconsole >> > - sources (complete, and those required for building apps) >> > - doxygen-generated docs >> > >> > -Steve >> > >> > >> > >> > --------------------------------------------------------------------- >> > Apache Qpid - AMQP Messaging Implementation >> > Project: http://qpid.apache.org >> > Use/Interact: mailto:[email protected] >> > >> > >> >> >> >> -- >> Martin Ritchie >> >> > --------------------------------------------------------------------- >> 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] > > -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
