Oh I was looking on an older version of BUILDING.md.. Thanks, I will try with your instructions.
Gal -----Original Message----- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Thursday, January 26, 2017 17:24 To: dev@geode.apache.org Subject: Re: C++ native client compilation in Visual Studio Native client is targeted for 64 bit only but that said you should have success on 32 bit, though your milage may vary. You have diverged considerably from BUILDING.md https://github.com/apache/geode/blob/next-gen-native-client-software-grant/BUILDING.md If you are using 32bit you need to specific the VS 32bit generator. $ cmake -G "Visual Studio 12 2013" ../src (notice the omission of the Win64 designation) Then open the nativeclient.sln file in the root of your build directory. You should not need to provide any paths since all that is handled when the solution and projects are generated by CMake. This current source is not compatible with ACE 6.3. The dependencies build will download and compile ACE 6.4.1. -Jake On Thu, Jan 26, 2017 at 7:11 AM Gal Palmery <gal.palm...@amdocs.com> wrote: I did, thanks, but I'm not sure how to use it.. I need to compile on VS 32 bit. The steps I took: 1) Open the gfcppcache.vcxproj in Visual Studio 2013, 32 bit, 2) Setting path to ACE (version 6.3.4) and to libxml in the project properties include directories, 3) try to compile it (unsuccessfully .. ) currently failing on many errors like this one: "error C1017: invalid integer constant expression" Thanks, Gal -----Original Message----- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Thursday, January 26, 2017 16:16 To: dev@geode.apache.org Subject: Re: C++ native client compilation in Visual Studio Can you share the steps you took? Did you follow the BUILDING.md file? On Thu, Jan 26, 2017 at 6:09 AM Gal Palmery <gal.palm...@amdocs.com> wrote: > Hi All, > > Did anyone successfully compile the c++ native client on Windows in > Visual Studio and can share some instructions ? > I'm struggling with it.. :\ > > Thanks, > Gal > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at http://www.amdocs.com/email_disclaimer.asp > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
