On Tue, 2016-07-05 at 13:33 -0700, loremIpsum1771 wrote:
> Yes, "<home>" is just being used as a placeholder. I created a new
> builds/qpid directory on the C drive and then ran the command: cmake
> -G
> "Visual Studio 12 2013" C:\Users\I664761\Downloads\qpid-cpp-0.34
> after doing
> which I got the following error log:
> https://gist.github.com/loremIpsum1771/fc1d912bbe5a741325cdd259f7a538
> 37
> 
> My company has a separate software package install manager through
> which I
> have to do installations. I already had python installed and had the
> environment variable set up and I downloaded ruby as well and set up
> the
> environment variable for it. I tried installing Valgrind through my
> company's software center but it seems that the closest thing to it
> is
> something calledLISA Dev Workstation. I couldn't find SASL and
> Doxygen
> within my company's software center. After configuring the paths for
> the
> installations, ran the command from above and got the error log. Are
> all of
> these packages required for the build? It seems like its only taking
> issue
> with not being able to find Ruby even though I set the path to it.

I'm pretty sure that the only thing required to build for the source
tarball is boost - You must install this (make sure you get the correct
version for your compiler and 32/64 bits).

When compiling on windows I don't think you need anything else - ruby
and python are used to generate some code that I think is pregenerated
in the source tarball (if I'm wrong about that then you will need
those)

As far as I know valgrind is Unix only and only used to run tests.
Python is also necessary to run some tests.

If you want to support amqp 1.0 you will also need qpid-proton.

You may find looking at the included appveyor.yml file useful - this is
the file that sets up the public CI build.

Andrew


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

Reply via email to