Sorry, I forgot to mention that I'm trying to build release_0_2_0 of the driver.
I still haven't figured this out but, knowing that it's possible, I started digging deeper. It appears to be an issue with the cmm_bridge depending on libssh2 (i.e., libssh2-1.4.3) and libssh2 depending on pthreads -- which I don't have. The other parts of the C++ driver seem to be getting their thread requirements satisfied by boost (i.e., boost_thread-vc100-mt-1_54.lib). Again, I'm still digging deeper but thought I toss this detail out in case it sparks the memory of anyone who's blazed this trail before. John -----Original Message----- From: Green, John M (HP Education) Sent: Tuesday, March 04, 2014 3:02 PM To: user@cassandra.apache.org Subject: RE: Datastax C++ driver on Windows x64 Thanks Michael. This is the "ray of hope" I desperately needed. I'll let you know how it goes. -----Original Message----- From: Michael Shuler [mailto:mshu...@pbandjelly.org] On Behalf Of Michael Shuler Sent: Tuesday, March 04, 2014 2:58 PM To: user@cassandra.apache.org Subject: Re: Datastax C++ driver on Windows x64 On 03/04/2014 04:30 PM, Michael Shuler wrote: > On 03/04/2014 04:22 PM, Michael Shuler wrote: >> On 03/04/2014 04:12 PM, Dwight Smith wrote: >>> Second that question >>> >>> *From:*Green, John M (HP Education) [mailto:john.gr...@hp.com] >>> *Sent:* Tuesday, March 04, 2014 2:03 PM >>> *To:* user@cassandra.apache.org >>> *Subject:* Datastax C++ driver on Windows x64 >>> >>> Has anyone successfully built the Datastax C++ driver for a Windows >>> 64-bit platform? >>> >>> While I've made some progress I'm still not there and wondering if I >>> should give-up and use a local socket to another process (e.g., JVM or >>> .NET runtime) instead. I'd prefer to use C++ because that's what the >>> rest of the application is using. However, my C++ and makefile >>> experience is very dated and I've never used cmake before. Still I'd >>> be very interested to know if anyone had success using the C++ >>> driver on Windows x64. >> >> http://cassci.datastax.com/job/y_cpp_driver_win32/lastBuild/consoleFu >> ll >> >> Please, let me know, and I'll dig for some further details, if this >> doesn't fully help. I did not set this particular job up, but >> jenkins runs the following batch script after git pull: >> >> ---- >> @echo off >> cd C:\jenkins\workspace >> mkdir y_cpp_driver_win32\bin >> copy CMakeCache.txt y_cpp_driver_win32\bin cd y_cpp_driver_win32\bin >> cmake . >> msbuild ALL_BUILD.vcxproj >> msbuild UNINSTALL.vcxproj >> msbuild INSTALL.vcxproj >> ---- > > I may have replied a bit too quickly - it does look like this is using > all 32-bit libs in the includes, even though it's built on a 64-bit > machine. > > You might be able to touch base with the developers on the freenode > #datastax-drivers channel. > I uploaded the CMakeCache.txt that is being copied over so you could peek at it, too. http://cassci.datastax.com/userContent/y_cpp_driver_win32-config/ -- Michael
