Xapian 1.2.0 arrives

Xapian 1.2.0, the first of a new ‘stable’ release series, was announced a few weeks ago and we’ve just uploaded pre-built binaries for Windows and associated build files. You can find them on our Xapian downloads page.

This version features a new, faster, more compact database format and enhanced backwards compatibility with existing databases; a built-in replication system (so in a distributed system you only need to propagate the changes to a Xapian database across the network); a “Match Spy” interface to allow information about search results (such as facets) to be gathered efficiently; subclassable “Posting Sources” to allow extremely flexible search customisations and many more improvements and bug fixes. Nearly all of these improvements have been available previously in the 1.1 ‘development’ series – you can find out more about how development and stable releases differ on the Xapian RoadMap page.

6 thoughts on “Xapian 1.2.0 arrives

  1. I have compiled 1.0.20 success, but when I built Xapian 1.2.0 in the same environment today, it can’t compile success.Is there are any differences between two version’s config ?
    Is there any one has the same question with me?

  2. Now,I use vs2010 compile the sourcefile,I can get all the libs,but I got error message like this:

    ..win32Releasexapian-compact.exe.manifest : general error c1010070: Failed to load and parse the manifest. {_~
    NMAKE : fatal error U1077: ‘”C:Program FilesMicrosoft SDKsWindowsv7.0Abinm
    t.exe”‘ : return code ‘0x1f’
    NMAKE : fatal error U1077: ‘”C:Program FilesMicrosoft Visual Studio 10.0VCBI
    Nnmake.EXE”‘ : return code ‘0x2’

    So,I remove all the contents like ‘$(MANIFEST) “$(OUTDIR)xapian-compact.exe.manifest” -outputresource:”$(OUTDIR)xapian-compact.exe;1″
    -@erase “$(OUTDIR)xapian-compact.exe.manifest”‘ in win32/win32_bin.mak and win32/win32_examples.mak. Then I got all libs and exe file.

  3. Ah – we haven’t yet tested the build files with VS2010, which may be causing your issue. Anyway, it sounds like removing the manifest compilation steps has solved your problem.

    • Hi, I’m afraid we don’t maintain these any more: also it’s been several years since we did, so anything we do have is likely to be rather out of date. There are some other options at the bottom of this page.

Leave a Reply

Your email address will not be published. Required fields are marked *