similar to: MSVC project file

hi i?m trying to build the ruby bindings in xapian 1.1.2 on win xp. i?ve 1. pulled the tags/1.1.2 revision from svn 2. built SWIG from repo via MinGW and MSYS (swig -help works, so build seems ok to me) 3. built xapian-core following readme in ...\win32msvc, apitest doesn?t give errors now if i try to build: "...\ruby>nmake SWIGBUILD=1 Microsoft (R) Program

I'm currently seeing: utils.cc c:\src\xapian\xapian-core\common\utils.h(84) : error C2061: syntax error : identifier 'mode_t' c:\src\xapian\xapian-core\common\utils.h(85) : error C2065: 'mode' : undeclared identifier I *think* I've done everything correctly this time in terms of updating svn and rebuilding :) My solution was to add: typedef int mode_t; to safestat.h -

Hello, i am trying to install xapian on windows. As the xapian download page says, there are two options here: 1) mingw 2) a separate set of makefiles for MSVC. If i understand correctly, MSVC is supported only by xapian 1.2.8 and older, so i decided to try mingw. The configure script worked perfectly, but "make" finished with a error (see the output below). So far i have two

I was chugging along following the various mailing list postings on how to build Xapian on windows when I got to the python bindings step and hit a snag. It seems that since I used a MSVC build of python (version 2.4) and that I'm doing a cygwin build of xapian I will have nothing but grief. :) First I tried the CPPFLAGS=-DPY_LONG_LONG="long long" fix for the error:

hi, anyone know how to build Xapian on windows?I had try this(https://github.com/xapian/xapian/tree/v1.2.24/xapian-maintainer-tools/win32msvc) but fail. error messages: .\remoteconnection.cc(532) : error C2146: syntax error : missing ';' before identifier 'uoff_t' How to edit the config.mak file to release a correct config.h file ? I can compile Xapian on Linux, it's easy, but

Hello, Thank you very much for quick response. I need only xapian-core. As I wrote on my case compilation with Visual Studio 2015 successful, just I have runtime errors, while the same code on LINUX runs fine. I'll try the hints from (https://trac.xapian.org/browser/git/xapian-core/INSTALL?rev=RELEASE/1.4#L54) and maybe to migrate my project to VS2017 and test it again. If I understand

The disclaimer automatically added and is not intended to limit legitimate discourse, and any code I write for this is expected to be licensed under whatever license the original work is using. I haven't tried compiling latest code under visual studio yet (is this possible?). I wonder if there is a way to tell gcc to not mangle the names during cross compile. I was able to successfully

On Tue, Jun 30, 2015 at 12:30:35PM -0700, Eric Lindblad wrote: > I don't know if it would be of any use - and I know that > the configure script searches for gawk, sed and grep - > but Watcom has free 32 and 64 bit compilers, and > the msvc files for Xapian no longer appear to be > maintained, so perhaps Xapian build files written for > [Open] Watcom could be made, as such

Ok, got my corrupted binary issues sorted out by having someone download the file for me and forward me the extracted contents. Bizarre, but fixed. Now, I'm running into another issue, this time with the Python bindings. I've installed the MSVC distrib package and checked that site-packages has `xapian.py` and a folder called `xapian` with three files in it: `__init__py`, `_xapian.pyd`

> It's close to irrelevant when they last worked at this point - the current > stable release series is 1.4.x, and they definitely won't work with that. acknowledged Visual Studio 2008, win32 makefiles (from C. Hull's website) and xapian-core-1.2.8 are mentioned together on this webpage https://lists.xapian.org/pipermail/xapian-devel/2012-October/001883.html

hi, I'm new in xapian project. I want to build 64bit xapian(1.2.8) from source using MSVC 2017. But I cann't find any documents about 64bit compiling steps. I tried to replace the WIN32 with the WIN64 in the source files, then compile all the source. But the query parser compiling failed. It seems the lemon.exe get a runtime error. Is there a official doc to

Hi all, I'm running out of time tonight, but I thought I would fire off this patch to the MSVC makefiles, which should get things building again (assuming you have a built zlib static library hanging around). I'll try and get to Olly's (private) request regarding buildbot and cygwin as I get time over the next few days. Cheers, Mark -------------- next part -------------- An

I think we should seriously consider requiring a compiler with C++11 support for the next Xapian stable release series (i.e. Xapian 1.4.x). There's not a firm timeline for when 1.4.0 will be out, but it's a way off yet. I need to sort out the blockers for 1.3.2 and actually get that out, and then we need to sort through the ticket pile and decide what has to get done. C++11 adds a

hi, I have read the install document,https://github.com/xapian/xapian/blob/v1.4.10/xapian-core/INSTALL,but don't how to build xapian project by MSVC. I execute command in mingw64.exe: ./configure CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS=-EHsc AR=lib has some errors: # ./configure CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS=-EHsc

On Tue, Mar 20, 2018 at 06:30:07PM +0000, Olly Betts wrote: > https://lists.xapian.org/pipermail/xapian-discuss/2018-January/009585.html Related to this, the appveyor build is currently failing on git master. Unfortunately the change at which is started to fail was the addition of the new "honey" backend, which doesn't narrow things down to a useful degree. I've checked over

Thanks for your reply. I had run vcvars64.bat,but still cann't find 'cl'. Finally I fix it, change msys2_shell.cmd: "if it is present: replace rem set MSYS2_PATH_TYPE=inherit with set MSYS2_PATH_TYPE=inherit". And other errors : # ./configure CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS="-EHsc AR=lib -IC:\zlib-1.2.3-lib\include

Hey Richhiey, Most probably Xapian is used with CYGWIN in Windows and Windows Specific Code in Xapian is based on CYGWIN, However we would be able to help you out with this issue, if you could pastebin whole 'gnu-make' generated report. Regards, Abhishek On Sat, Jan 3, 2015 at 5:30 PM, <xapian-discuss-request at lists.xapian.org> wrote: > Send Xapian-discuss mailing list

On Thu, Apr 12, 2007 at 12:52:03PM +0100, richard wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: richard > Revision: 8196 > Date: 2007-04-12 12:52:02 +0100 (Thu, 12 Apr 2007) > > Log message (1 line): > Fix rules for generating .pl files from .pl.in files. > > Modified files: > U

I tried to compile xapian 1.0.1 under windows but the new /msvc/version.h file has #undef XAPIAN_HAS_REMOTE_BACKEND which prevents /backends/dbfactory_remote.cc to be built. The old (hand-written) version.h.win32 had it defined to 1. Everything build fine if I replace #undef with #define in version.h. Cheers, -- Daniel M?nard

Hi, folks. I don't know much about C++, so please excuse my newbie question: I just tried to include Xapian in a dummy Cocoa project, ie created a new project and added the libxapian.a file installed via MacPorts. When I include xapian.h in an Objective-C++ file (either mm or h), the compilation fails with the following message: ================= In file included from