Please ignore my last email. There was a problem with the PATH environment variable.
> From: [email protected] > To: [email protected] > Subject: RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013 > Date: Fri, 27 May 2016 11:40:58 +0200 > > Hello Justin, > I updated to the head of the trunk and relaunched everything. I still have a > problem with the qpid tools.I can see all the bat files, but the code still > calls the original files for example: > 1: run_acl_tests: Calling 'qpid-python-test --broker localhost:63666 --time > -m acl -Dport-i=63668 -Dport-u=63710 -Dport-q=63712 > -Dpolicy-file=D:\qpid-cpp-trunk.git\qpid\qpid\cpp\build-dir-RelWithDebInfo\src\tests\policy.acl'1: > 'qpid-python-test' is not recognized as an internal or external command, > All the .py files have not been updated to launch qpid-python-test.bat when > on windows:Example: > qpid/cpp/src/tests/run_interop_testscall("qpid-python-test -m interop_tests > -DOUTDIR={0}", WORK_DIR) > Regards,Adel > > Date: Thu, 26 May 2016 15:02:59 -0700 > > Subject: Re: Qpid C++ 0.34 unit tests are failing with visual studio 2013 > > From: [email protected] > > To: [email protected] > > > > An update. I think I've fixed the python and backslash problems. > > > > https://issues.apache.org/jira/browse/QPID-7281 > > > > Here's what I get now in appveyor: > > > > > > https://ci.appveyor.com/project/ssorj/qpid-svn-reorg/build/hammerandtong.71 > > > > The unit_test failure is one I've had for a long time. I've not yet been > > able to convince either appveyor to use "localhost" for its hostname or > > unit_test to use "appveyor-vm" as its ssl cert name. So it times out. > > > > The other tests are running now, with some failures. Note that up to now > > I've been liberal in enabling the cross-platform tests that can > > hypothetically work in windows. There may be specific instances where I'm > > wrong, and we'll need to adjust the target platform for the test. > > > > On Thu, May 26, 2016 at 9:45 AM, Andrew Stitcher <[email protected]> > > wrote: > > > > > On Thu, 2016-05-26 at 09:38 -0700, Justin Ross wrote: > > > > I tried this approach first. I wasn't able to make that > > > > configuration > > > > available in CTestCustom.cmake when I tried last. However, I don't > > > > think I > > > > tried repeating the find_package logic directly in the custom.cmake > > > > file, > > > > which I will do. > > > > > > CMake is hierarchical so the find_package() would need to be in a CMake > > > file above the relevant one (and perhaps in the sequence before the > > > add_directory(..) or include(...) that includes the file you want the > > > definition in - I'm not too clear about that point. > > > > > > Andrew > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > >
