Thanks for asking!  But please note that AMQP-1.0 support on Windows
is incrementally being added at this point, with the latest bits being
SSL capability.  A push-button build and full ctest integration is
still in the future.  You will get the best results working from the
latest pending releases:

  http://people.apache.org/~rhs/qpid-proton-0.7rc2/

  https://svn.apache.org/repos/asf/qpid/branches/0.28/

I currently build by hand, loosely as follows:

- Choose 64 or 32 bit (or perform steps below twice in separate locations)
- Install pre-requisites: boost, python to match bit-ness
- Install cmake, ruby and swig (bit-ness doesn't matter)

- cmake Proton setting CMAKE_INSTALL_PREFIX=C:\some\path
- build INSTALL target for Proton in Visual Studio twice (Debug RelWithDebInfo)

- cmake Qpid as for Proton but also set CMAKE_PREFIX_PATH=C:\some\path
- confirm cmake says: "Qpid proton found, amqp 1.0 support enabled"
- if not check paths set in C:\some\path\lib\cmake\Proton\ProtonConfig.cmake
- build Debug and/or RelWithDebInfo versions

Be sure to read the README files.  That, plus the above should get you
going.  You will want to set your PATH to find python and ruby and
swig, set BOOST_ROOT and BOOST_VERSION, and be consistent about 32/64
bit-ness when setting environment variables or selecting Visual Studio
build options.

The magic for Qpid to "find" Proton has changed very recently, so
someone may suggest a better way to instruct cmake than I suggested
above.  With luck, someone may chime in and point you to a build
script if they have one.

Cliff

On Fri, Apr 4, 2014 at 5:11 AM, DHF <fhd_...@163.com> wrote:
> Hi MaryDHinton,
>
> could you share the steps how to get the Windows port of the amqp
> project in QPID compiled? i will very appreciate! Thanks.
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/PROTON-amqp-1-0-support-tp7585425p7606419.html
> Sent from the Apache Qpid developers mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to