similar to: Re: [Xapian-commits] Changes in xapian/xapian-bindings/ xapian/xapian-bindings/guile/ xapian/xapian-bindings/php4/ xapian/xapian-bindings/python/ xapian/xapian-bindings/tcl8/

On Tue, May 11, 2004 at 08:11:23PM +0100, Richard Boulton wrote: > Also, change tests for non-zeroness of interpreter paths to tests > for existence and executability of interpreter paths: this is > relevant if configure is passed an interpreter path by the user > which doesn't exist (as my debian packaging makefile just did). A problem is that "test -x"

Hi, I have been maintaining Guile bindings for Xapian for a few years now. Recently, I released guile-xapian 0.4.0. Happy for people to hack on it and use it in their projects! Project website: https://guile-xapian.systemreboot.net/ Git repository: https://git.systemreboot.net/guile-xapian/ Release 0.4.0 tarball: https://guile-xapian.systemreboot.net/releases/guile-xapian-0.4.0.tar.lz Tarball

Questions are threaded into the output: ******************** #./configure --without-python checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking

On Tue, May 11, 2004 at 05:41:58PM +0100, Richard Boulton wrote: > * If the queryserver can't parse a query, strip out all special > characters, and then retry. This means that we get some kind of > result even if the query is broken. That's probably a feature worth pushing down into Xapian::QueryParser... Cheers, Olly

Hi all. I have problem compiling xapian php bindings. I am using debian sarge. I have installed php4-dev before compilation. I am getting the following errors: boomer:~/xapian/xapian-bindings-0.9.0# make make all-recursive make[1]: Entering directory `/root/xapian/xapian-bindings-0.9.0' Making all in php4 make[2]: Entering directory `/root/xapian/xapian-bindings-0.9.0/php4' make

On Thu, May 20, 2004 at 02:55:13PM +0100, Richard Boulton wrote: > Add debian packaging files to distribution tarball. > > Modified files: > xapian-core : Makefile.am You also need to add debian/Makefile.in to configure.in (I usually forget too). Probably debian/control.in too. Cheers, Olly

On Thu, Oct 21, 2004 at 05:45:42PM +0100, Olly Betts wrote: > Log message: > python/docs/bindings.html: Remove documentation explicitly saying > how we wrap Xapian::QueryParser and Xapian::Stem since we wrap them > exactly as we wrap everything else we don't mention! Also mention > simpleexpand example. The point of this comment was to highlight that they exist within the

On Wed, Apr 11, 2007 at 10:31:39AM +0100, richard wrote: > python/smoketest.py: Replace cut-and-pasted test checking code > with functions, to simplify tests. It might be simpler, but mostly because functionality has gone - you've thrown away all my carefully written failure messages! Now if a test fails, the message is very generic and you have to read the code to find out what's

Question for people who have successfully used these bindings - how do I create a database object? I can't use open(), because it doesn't like the number of arguments, presumably because it's an overloaded method and hence we should rename it in PHP. So how do others do it? Or am I the only person trying to create a writable database object in PHP? :) J --

I'm having a problem compiling the python 2.1 packages for release 0.9.1 - I get many errors along the lines of: ../../python/olde/xapian_wrap.cc: In function `PyObject* PySwigObject_repr(PySwigObject*)': ../../python/olde/xapian_wrap.cc:664: error: `PyString_FromFormat' undeclared (first use this function) On further investigation, the copies of xapian_wrap.cc in the olde and

Currently, the SWIG generated bindings catch exceptions raised by Xapian and rethrow them using the standard SWIG error types: for example, if any Xapian::DatabaseError exception is raised, SWIG will use its standard SWIG_IOError error type to report the error. In Python, this leads to code like the following: try: db.get_document(1) except RuntimeError, e: if

Currently, the SWIG generated bindings catch exceptions raised by Xapian and rethrow them using the standard SWIG error types: for example, if any Xapian::DatabaseError exception is raised, SWIG will use its standard SWIG_IOError error type to report the error. In Python, this leads to code like the following: try: db.get_document(1) except RuntimeError, e: if

On Wed, May 24, 2023 at 02:18:50AM +0000, nebulaaksum wrote: > I have more question. After successfully installing xapian-bindings-1.4.22. I continued to install xapian-omega-1.4.22. But it did not even pass the configuration step. > I intend to install xapian-omega-1.4.22 at > /usr/local/xapian-omega-1.4.22. I do my building from a separate > build directory lest I clutter my

On Sat, Aug 09, 2003 at 01:12:51AM +0200, Nicolay Mausz wrote: > I'm currently writing another PHP4 binding without Swig. It is not a > full 100% implementation of the whole API (I think this will be the Swig > implementation) but it supports the most important features. Hi Nicolay, I just found this message while searching through my old mail. Did you release these PHP bindings?

Thank you very much,It works! And some Q&A I meet,may help somebody: 1. If zlib build with 32bit,should use MSVC's 'vcvars32.bat'; 2. Add '-Z7' to CXXFLAGS can release *.pdb file for VS2017 'Step Into' debug, such as: CXXFLAGS="-EHsc -Z7"; 3. If Somebody write a demo in VS2017 3.1 change libxapian.a's name to libxapian.lib; 3.2 make sure the

> Great, but which "it" worked? I had install mingw earlier, but not set it to $PATH, so must be 'LD=link' and your previous advices on "CXXFLAGS" . I execute configure like this: ./configure LD=link CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS="-EHsc -Z7" AR=lib CPPFLAGS=-IC:/zlib-1.2.3-lib/include

On Wed, Feb 20, 2019 at 12:41:07PM +0800, cswuyg wrote: > 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". OK, I'll note that in the instructions. It looks like you can also enable this option as a

On Thu, Apr 12, 2007 at 05:57:27PM +0100, richard wrote: > xapian.i: Parse the visibility support header file, so we don't > get errors when we %include other xapian headers. Fixes error > reported by python/except.i, which has a line saying > %include "xapian/error.h" That part is easy enough, but does "make check" now pass for you? My build is failing to

olly wrote: > Log message (6 lines): > backends/flint/flint_database.cc: Delete the corresponding entry > (if any) from doclens in delete_document(). Add assertion to > add_document_() that the corresponding entry in doclens isn't > already set, but in a non-debug build overwrite any existing > entry as that's more likely to be correct. >

I've released Xapian 1.2.22 (including Search::Xapian 1.2.22.0), which you can download from: http://xapian.org/download Since 1.2.16, release tarballs are compressed with xz instead of gzip, as it provides much better compression, without being too slow to decompress. (For now at least, Search::Xapian is still gzipped.) We decided not to provide multiple formats for the downloads. The