similar to: Project for a group of 5

Hi We would like to do the project on improving Java bindings. It is a GSoC project, although I guess we can take it up as such. But before we go ahead, we would like to have some details as to how much work it would be and also how would we evaluate the work done. (compare test cases / compare java code with c++ code ?) Is there any way in which we can quantify the improvements made to the API?

Oh. The diff file doesn't seem to include the two new files. We're outside right now. I'll send you the files as soon as we reach in 30-40 minutes. Also, we're moving to git. Thanks On Apr 13, 2014 9:12 PM, "James Aylett" <james-xapian at tartarus.org> wrote: > On 13 Apr 2014, at 16:16, Siddhant Mutha <siddhantmutha at gmail.com> wrote: > > > We

Here are the files. /include/xapian/trie.h /api/trie.cc *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/ <http:/www.siddhantmutha.com/> On Sun, Apr 13, 2014 at 9:33 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 16:59, Siddhant Mutha <siddhantmutha at

Oh, no no. It was a typo in the mail. We did the same thing you mentioned. *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/ <http:/www.siddhantmutha.com/> On Sun, Apr 13, 2014 at 11:31 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 18:56, Pallavi Gudipati

Hi We are writing a new module which needs to be added to the Xapian source. For this, what modifications are to be made to the Makefile? The two modules we are writing will be in the 'include' and 'api' folders. Cheers *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/

Hi The above problem has been resolved (it is detecting our new modules). We didn't have some dependencies installed and hence it was using an old Makefile. We installed them and now it is fine. Now, while running 'make', we get the following error: http://pastebin.com/VX1HWyJc *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai

It is there: https://github.com/sidmutha/xapian/blob/master/xapian-core/api/Makefile.mk#L53 On an other note, I'm trying to run ./bootstrap from the cloned repo. But it gives an error saying "unknown option -C" followed by "Bootstrap failed". *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai

We are using the --enable-maintainer-mode and will move to git soon. The diff file is attached. *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/ <http:/www.siddhantmutha.com/> On Sun, Apr 13, 2014 at 8:26 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:48, Pallavi

Configure command: ./configure --enable-maintainer mode I dont get any output with nm that contains Trie. On Sun, Apr 13, 2014 at 11:20 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 18:39, Pallavi Gudipati <pallavigudipati at gmail.com> > wrote: > > > I am working in Ubuntu 12.04. I have tried re-configuring the source > tree too.

trie.cc still isnt showing up. http://pastebin.com/c89kWz3L Also we have shifted to git: https://github.com/sidmutha/xapian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20140413/b82f4a92/attachment-0002.html>

Hi all, I was trying to generate lcov test coverage reports for xapian-core but got an out of memory error: $ lcov --capture --directory . --output-file xapian-core.info Capturing coverage data from . Found gcov version: 4.7.3 Scanning . for .gcda files ... Found 270 data files in . Processing bin/xapian-progsrv.gcda Out of memory! These are the steps I followed in xapian-core directory

My code is not on Github. I am using the tarball as of now. The following it the error that occurred: http://pastebin.com/cVJrjUZX On Sun, Apr 13, 2014 at 8:16 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:37, Pallavi Gudipati <pallavigudipati at gmail.com> > wrote: > > > A linker error is encountered even after following the above

Hi, Alan Thanks for making it clear. But I was more confused now :( I tested on a simple program and used both gcov and lcov to get branch coverage. The code and build commands as below: *Example simple.cc* #include <string> // If not comment this line, the branch coverage won't reach to 100% // #include <iostream> int main(int argc, const char* argv[]) { std::string str =

A linker error is encountered even after following the above steps. ERROR: undefined reference to `Xapian::Trie::Trie()' On Sun, Apr 13, 2014 at 8:00 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:24, Siddhant Mutha <siddhantmutha at gmail.com> wrote: > > > We are writing a new module which needs to be added to the Xapian > source.

All, Here are the latest patches to expreiment with gcov profiler for xen hypervisor. I have tested current patches on Intel i686. System Details: gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) gcov (Ubuntu 4.3.3-5ubuntu4) 4.3.3 Kernel 2.6.28-11-generic Distribution: Ubuntu jaunty 9.04 There are some design issue which i would like to highlight here: 1. To create gcov proc dir user /proc/xen, we are

All, Here are the latest patches to expreiment with gcov profiler for xen hypervisor. I have tested current patches on Intel i686. System Details: gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) gcov (Ubuntu 4.3.3-5ubuntu4) 4.3.3 Kernel 2.6.28-11-generic Distribution: Ubuntu jaunty 9.04 There are some design issue which i would like to highlight here: 1. To create gcov proc dir user /proc/xen, we are

The outputs: config.log : http://pastebin.com/tEBiCgcb lib_src: http://pastebin.com/mm7K7pFc On Sun, Apr 13, 2014 at 11:36 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 19:03, Siddhant Mutha <siddhantmutha at gmail.com> wrote: > > > Oh, no no. It was a typo in the mail. We did the same thing you > mentioned. > > Can you give me the

I am working in Ubuntu 12.04. I have tried re-configuring the source tree too. Removing the destructor stops the error messages for the destructor but the constructor's error persist. ERROR: http://pastebin.com/r0wYNfEs On Sun, Apr 13, 2014 at 10:56 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 17:49, Siddhant Mutha <siddhantmutha at gmail.com>

Hi, Alan Really very excited to receive your email and sorry to be slow replying, it has been exceptionally busy over the last few days ;( Your explanation made the problem clear to me. So gcov branch coverage should be called condition coverage and clang region coverage is branch coverage in fact(also known as *decision/C1*), right? And llvm/clang will support all the following coverage

Hi , I could see the LLVM code coverage info at the below links http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html http://llvm.org/reports/coverage/ I am interested in the branch coverage metric. I could not find the branch coverage related info . Can anyone let me know how to find it. If it is not available , I am happy to work on it, if I can get some details on why