headers
Morya | 1 Dec 06:53
Picon
Gravatar

build simpleindex.cc on windows using vc9 don't know libs

Dear All Guys,
   Hello there! Greetings!

   I am currently using VC9 to build xapian simplest sample simpleindex on
Windows.
   I have managed to build xapian, using the tool recommended at the bottom
of this page.
http://www.xapian.org/download.php (Compiling on MS Windows with MSVC)
   All the sample apps and test programs did successfully run, but when I
create a project from the code,
I don't know what libs should I include... There are so many libs, in the
"Release" folder.

   I tried to add all of them to my project, but I still got 20 errors
complaining that
some external symbols missing.
   I thought of reading the Makefile myself, but, obviously, it's not a easy
job for me.

   Can anybody tell me what I am doing wrong here, thanks a lot!

Best Regards
Morya

------------------------

1>libbackend.lib(dbfactory_remote.obj) : error LNK2001: unresolved external
symbol __imp__WSAStartup <at> 8
1>libbackend.lib(dbfactory_remote.obj) : error LNK2001: unresolved external
symbol __imp__WSACleanup <at> 0
(Continue reading)

Permalink | Reply | 3 comments |
headers
Olly Betts | 1 Dec 07:41
Favicon
Gravatar

Re: build simpleindex.cc on windows using vc9 don't know libs

On Mon, Dec 01, 2008 at 01:53:30PM +0800, Morya wrote:
> I don't know what libs should I include... There are so many libs, in the
> "Release" folder.

Yeah - I think we really should be building a single DLL here rather
than statically linking against a huge number of libraries.

>    I tried to add all of them to my project, but I still got 20 errors
> complaining that
> some external symbols missing.

Sounds like you're missing the external dependencies of lib and winsock.

>    I thought of reading the Makefile myself, but, obviously, it's not a easy
> job for me.

Me neither - I'm afraid I don't know how you're meant to specify those
dependencies, but looking at how "omega" is built should reveal what's
needed.

Cheers,
    Olly
Permalink | Reply | 2 comments |
headers
Morya | 1 Dec 08:04
Picon
Gravatar

Re: build simpleindex.cc on windows using vc9 don't know libs

Hi Olly,
Thx a lot !!!

When I add ws2_32.lib to the project, error messages reduced to 7.
Then I googled about the "inflateEnd" external symbol, I got some one
mentioned zdll.lib,
I tried, then, Bong, It works!
Now, I got a simpleindex.exe here~.

Best regards
Morya

2008/12/1 Olly Betts <olly <at> survex.com>

> On Mon, Dec 01, 2008 at 01:53:30PM +0800, Morya wrote:
> > I don't know what libs should I include... There are so many libs, in the
> > "Release" folder.
>
> Yeah - I think we really should be building a single DLL here rather
> than statically linking against a huge number of libraries.
>
> >    I tried to add all of them to my project, but I still got 20 errors
> > complaining that
> > some external symbols missing.
>
> Sounds like you're missing the external dependencies of lib and winsock.
>
> >    I thought of reading the Makefile myself, but, obviously, it's not a
> easy
> > job for me.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Olly Betts | 1 Dec 08:47
Favicon
Gravatar

Re: build simpleindex.cc on windows using vc9 don't know libs

On Mon, Dec 01, 2008 at 06:41:32AM +0000, Olly Betts wrote:
> Sounds like you're missing the external dependencies of lib and winsock.

Sorry, typo - that should read "zlib and winsock".

Cheers,
    Olly
Permalink | Reply | 0 comments |
headers
Olly Betts | 1 Dec 09:02
Favicon
Gravatar

Re: undefined reference to "function name"

On Wed, Nov 26, 2008 at 12:33:10AM -0500, Zhiguo Li wrote:
> Maybe my last email was too long, and I will simplify it:

No - you just shouldn't necessarily expect an answer in less than two
days.  We do our best to make sure that mail to the lists gets answered
fairly promptly, but it's not something anyone is paid to do and
sometimes everyone who knows the answer is just busy or away.

You don't say if you're building from tarballs or SVN, or how you're
configuring, but I think your problem is probably that you aren't using
--enable-maintainer-mode when running configure (so your changes to
matcher/Makefile.mk have no effect).  See HACKING for details (and much
more information you'll find useful if you want to modify Xapian).

Cheers,
    Olly
Permalink | Reply | 2 comments |
headers
Olly Betts | 1 Dec 10:56
Favicon
Gravatar

Re: Size of the index

On Mon, Nov 24, 2008 at 03:47:27PM +0100, Justine Demeyer wrote:
> I indexed a set of 200 000 data who has a global size of about 1Gb and the
> index created has a size of more than 3Gb!! What can explain this
> difference???

I've added a new FAQ entry about database size:

http://trac.xapian.org/wiki/FAQ/DatabaseSize

Hope that helps.

Cheers,
    Olly
Permalink | Reply | 3 comments |
headers
Olly Betts | 1 Dec 11:06
Favicon
Gravatar

Re: Remote() support for Perl

On Wed, Nov 26, 2008 at 04:08:11PM +0100, Markus Wörle wrote:
> I actually need it now, and wrote a patch (which is attached).

I don't see a patch - just an empty attachment.  Perhaps the list
mangled it?  Probably better to post a link or open a ticket for it in
trac.

> Would it be possible to include it in further releases (at least until  
> SWIG C++ to Perl is available)?

Well, I can't promise for an unseen patch, but probably yes if it works,
includes any appropriate documentation updates, and adds test coverage
(so that we know it works and will continue to!)

Cheers,
    Olly
Permalink | Reply | 2 comments |
headers
Henry | 1 Dec 11:39
Picon

Re: Size of the index

Quoting "Olly Betts" <olly <at> survex.com>:
> http://trac.xapian.org/wiki/FAQ/DatabaseSize

"...This change reduced the size of gmane's compacted postlist.DB by 44%!"

Any idea when that new format will see the light of day in stable?   
44% will make an incredible difference in so many ways...  of course,  
this is dependent on your index structure, etc, but still.

Cheers
Henry Combrinck
Permalink | Reply | 2 comments |
headers
Markus Wörle | 1 Dec 12:03
Picon

Re: Remote() support for Perl


Am 01.12.2008 um 11:06 schrieb Olly Betts:

> On Wed, Nov 26, 2008 at 04:08:11PM +0100, Markus Wörle wrote:
>> I actually need it now, and wrote a patch (which is attached).
>
> I don't see a patch - just an empty attachment.  Perhaps the list
> mangled it?  Probably better to post a link or open a ticket for it in
> trac.

Uhm, it seemed properly atached in my sentbox copy, anyway, here is a  
link: http://mrks.de/xapian/remote-patch

>> Would it be possible to include it in further releases (at least  
>> until
>> SWIG C++ to Perl is available)?
>
> Well, I can't promise for an unseen patch, but probably yes if it  
> works,
> includes any appropriate documentation updates, and adds test coverage
> (so that we know it works and will continue to!)

I see. My patch does neither include documentation nor test-cases so  
far. Since I am slightly busy right now and don't get around to fixing  
this promptly, I just linked the current patch for completeness.

Regards,
mrks
Permalink | Reply | 1 comment |
headers
Olly Betts | 1 Dec 12:04
Favicon
Gravatar

Re: writing match deciders / custom handling of terms

On Sat, Nov 29, 2008 at 07:57:24PM +0200, djcb wrote:
> On Thu, 13 Nov 2008, Olly Betts wrote:
> > It works well in the case where you want to precisely match an exact value,
> > or one of a small number of values.  It doesn't really matter if
> > there's a handful
> > of flags or thousands, it's how you want to search for them which matters.

> Well, I have a bunch of flags, and I'd like to match all new messages that
> are encrypted but don't have attachments:
>     flags:NX^A
>   
> (X means 'encrypted', '^' means 'not')
> 
> In my current implementation, I simple translate that in number, and do
> a bitwise-OR with a number in the database. This is quite hard with
> Xapian; it's doable, but it will require quite some tricks.

I don't actually see how you implement this with a bitwise-OR, but
anyway with Xapian I'd just index it as a set of boolean terms - e.g.
XFLAG:N XFLAG:X XFLAG:A and a document only gets the term for a flag if
the flag is set.

Then "flags:NX^A" translates to: ((XFLAG:N AND XFLAG:X) AND_NOT XFLAG:A)

> > Yes (though I'm not sure how an empty range end is handled currently).
> 
> Well, I think I have to pre-process queries before I feed them to the
> QueryParser. What would be nice is some control over how individual
> elements are parsed (eg. the flags:NX^A example above).
(Continue reading)

Permalink | Reply | 0 comments |

Gmane