First thanks to both Justin and Chuck for your responses there nothing like a community that steps up to help!
I am a consultant/contractor doing primarily application development which means I am "tied" to the "wishes" of the client and in this case that the code base be developed in Visual Studio 17. The main issue has been CMake and an apparent incompatibility with MSBuild. It appears that the order in which objects need to be compiled has been "compromised" or else there is an inconsistency in being able to navigate to find items such as folder and compilation tools. I will review the discussion and see if I can make specific progress. In the meantime can someone point me to a discussion/description of the order in which objects need to be built? Thanks again to Justin and Chuck. Paul ________________________________ From: Chuck Rolke <[email protected]> Sent: Tuesday, November 14, 2017 8:40 AM To: [email protected] Subject: Re: Need help compiling in Visual Studio QPID C++ I tried https://ci.appveyor.com/project/ChugR/qpid-cpp , a manual configuration (ignoring qpid-cpp appveyor.yml) using Visual Studio 2013 and before-build script: mkdir BLD cd BLD cmake -G "Visual Studio 12 2013" -DBUILD_BINDING_DOTNET=OFF -DBOOST_ROOT=C:\Libraries\boost -DBOOST_LIBRARYDIR=C:\Libraries\boost\lib32-msvc-12.0 .. cd .. This compiled successfully using the default version of Boost. It barfed later with ctest issues but the goal was compilation. In my experience the qpid-cpp Windows builds suffer from a steady stream of bit rot from new versions of MSbuild, cmake, boost, and qpid-proton. The remedy is to keep building the latest-and-greatest with all the new tools and libraries and fix problems as soon as they appear. I recently upgraded some scripted builds using Visual Studio 2017 and found drastic behavior changes. I got my scripts to work but VS2015 and VS2013 could be scripted more easily following the same model as previous versions of Visual Studio. Discussion http://qpid.2158936.n2.nabble.com/Building-Qpid-on-Windows-td7622672.html is still relevant with respect to getting qpid-cpp and qpid-proton (qpid-cpp's AMQP 1.0 engine) to work together as designed. ----- Original Message ----- > From: "Justin Ross" <[email protected]> > To: [email protected] > Sent: Monday, November 13, 2017 7:38:36 PM > Subject: Re: Need help compiling in Visual Studio QPID C++ > > Hi, Paul. What are the errors you are seeing? > > I gave it a try on AppVeyor, and I immediately ran into a problem with a > newer version of msbuild. > > https://ci.appveyor.com/project/ssorj/qpid-cpp/build/1.0.13 > > Chuck, what does that portend? Do we need to generate new build metadata > for Windows? > > On Mon, Nov 13, 2017 at 2:22 PM, Flores, Paul A. <[email protected]> > wrote: > > > Help! > > > > > > CMake is not cooperating/working with Visual Studio and I am about running > > out of hair to pull! Only issues in the Linux world were self induced not > > sure about this windows environment! > > > > > > Can anyone give me a bit of help? I have a very narrow window to prove > > QPID is a viable alternative for a new manufacturing application, > > > > > > Any help would be greatly appreciated to get QIP CPP compiled! > > > > > > Paul > > > > > > ________________________________ > > > > This communication (including any attachments) may contain information > > that is proprietary, confidential or exempt from disclosure. If you are not > > the intended recipient, please note that further dissemination, > > distribution, use or copying of this communication is strictly prohibited. > > Anyone who received this message in error should notify the sender > > immediately by telephone or by return email and delete it from his or her > > computer. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ________________________________ This communication (including any attachments) may contain information that is proprietary, confidential or exempt from disclosure. If you are not the intended recipient, please note that further dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who received this message in error should notify the sender immediately by telephone or by return email and delete it from his or her computer.
