similar to: Resource version in php_xapian.dll (windows)

I noticed this footnote in deprecation.rst: .. [#version] The version functions will probably be preserved for longer than the usual lifetime of deprecated features, because it is unhelpful to remove functions which people use to test the version of the library in use. However, the replacements have been supported for long enough that new applications should use the

Hi, I'm the current developer of Xapian-Haystack, and I'm glad to announce that we've been finally able to install and pass all the tests of Xapian-Haystack with Xapian 1.3.3 in both Python 2 and 3, which means that Xapian-Haystack now supports Python 3. This naturally would not be possible without your efforts to push Xapian bindings to Python 3, and I thank you for that. Here I

Resurrecting an old thread from 2012! Finally got back to working on this. I have been stuck in JavaScript land for too long. Come to find out, on windows, perl does indeed define open to be win32_open and close to be win32_close. This is done in perl/lib/CORE/win3iop.h. So, to get past this problem, I had to modify Xapian.xs to do an #undef of open and close if WIN32 is defined. Also, I had

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

Hi, I've a problem to integrate xapian in my web application. I've developed the code for index e for search the documents published through my application. The app is developed in PHP. I've created a file that contain some function for search (called simpleSearch and advSearch). The problem is that if i run the code through the IDE (Zend for Eclipse) as PHP script it work correctly,

Hi All Is there any reason why someone could not build a regular PHP extension (not using SWIG) for Xapian? Same as mnoGoSearch has. The extension itself would be released under the PHP license. Is there anything on either side of the pond that would prevent this from being legal? Alec

Very odd this, I have downloaded the latest xapian-core and bindings. Installed xapian-core no problem in /usr/local/xapian However I am getting very strange errors when running make when trying to install the PHP bindings, it configures fine. Paste bin here: http://pastebin.com/JWViJz4b I am missing something obvious I know... I have built 1.0 on this machine in the past fine... John

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of

Here is the output I get from nmake. I am not a guru at getting C programs to build under windows, I never had any troubles I could not solve on OSX :-( I am using the released sources, I have Visual Studio 2005, I have the make files from lemur. I read ALL the readme.txt file before starting. And this is what I get. C:\Documents and Settings\jroberson\My Documents\DOWNLOADS\xapian-