hi lars

glad you're trying to use the eclipse file. I use it everyday, but no-one
else seems to use it. I can help you. Please follow the instructions below,
don't diverge from it



On 3 June 2014 12:39, Lars Bungum <lars.bun...@idi.ntnu.no> wrote:

>  Hi Hieu,
>
> thanks!
>
> It's a lot better now.  I'm going to do some feature development (for DA
> purposes), so I would like to get into the code, kind of to get a better
> feel of what I'm working on.
>
> It mostly works now, after adding the directory mosesdecoder/lib to the
> g++ linker includes in Eclipse (or doing it manually at the command line).
>
don't copy or add mosesdecoder/lib to Eclipse. The libraries in there are
compiled by bjam. You need the libraries compiled by Eclipse to be able to
debug it

>
> What remains now are several errors from DALM when building moses itself.
> To me this sounds like a version error, as it seems to pertain to arity
> changes, e.g.
>
> mosesdecoder/moses/LM/DALMWrapper.cpp: In member function ‘virtual void
> Moses::LanguageModelDALM::Load()’:
> mosesdecoder/moses/LM/DALMWrapper.cpp:213:48: error: no matching function
> for call to ‘DALM::LM::LM(std::string&, DALM::Vocabulary&, DALM::Logger&)’
> mosesdecoder/moses/LM/DALMWrapper.cpp:213:48: note: candidates are:
> mosesdecoder/contrib/other-builds/../../DALM/include/dalm.h:23:4: note:
> DALM::LM::LM(std::string, DALM::Vocabulary&, unsigned char, DALM::Logger&)
> mosesdecoder/contrib/other-builds/../../DALM/include/dalm.h:23:4: note:
> candidate expects 4 arguments, 3 provided
> mosesdecoder/contrib/other-builds/../../DALM/include/dalm.h:22:4: note:
> DALM::LM::LM(std::string, std::string, DALM::Vocabulary&, size_t, unsigned
> int, DALM::Logger&)
>
> I just downloaded the latest DALM version and compiled it.  Is this the
> correct one?
>
I use the DALM directly from github
   https://github.com/hieuhoang/DALM
I've just updated my own version, clean and compile both DALM, bjam moses,
and Eclipse moses. They all work

>
> //LB
>
>
> On 03. juni 2014 10:49, Hieu Hoang wrote:
>
>   Some advise:
>    1. Only use the eclipse build if you intend to debug & change the C++
> code. There's no other reason otherwise
>    2. You must switch your workspace to
>            {MOSES}/contrib/other-builds
>   3. There is no flexibility in what external libraries you need to link
> to. You must link to
>           i. boost
>          ii. DALM
>         iii. irstlm
>          iv. randlm
>           v. srilm
>        If you've never used these libraries before, I suggest you use the
> Moses bjam build 1st and make sure the external libs are properly compiled.
>     4. The external libs must be in the root of the moses folder, with
> specific names. I softlink them to my moses folder. For example, this is
> the listing of my moses folder:
>     #ls -l
>    drwxr-xr-x  3 hieu hieu    4096 Jan 15 11:05 biconcor
> drwxrwxr-x  2 hieu hieu    4096 Jun  2 18:17 bin
> -rwxr-xr-x  1 hieu hieu     780 Jan 15 10:58 bjam
> lrwxrwxrwx  1 hieu hieu      39 Jan 20 16:23 boost ->
> /home/hieu/workspace/boost/boost_1_55_0
> -rw-rw-r--  1 hieu hieu     119 May 30 09:30 BUILD-INSTRUCTIONS.txt
> drwxr-xr-x 24 hieu hieu    4096 Apr 30 16:50 contrib
> drwxr-xr-x  3 hieu hieu    4096 Jan 15 10:58 cruise-control
> lrwxrwxrwx  1 hieu hieu      33 Jan 20 16:23 DALM ->
> /home/hieu/workspace/github/DALM/
> drwxr-xr-x  2 hieu hieu    4096 Mar 12 19:27 defer
> -rw-r--r--  1 hieu hieu    3399 May 12 19:43 err
> -rw-r--r--  1 hieu hieu 2473076 Mar 21 21:17 err.ubuntu13.10
> lrwxrwxrwx  1 hieu hieu      27 Jan 20 16:23 irstlm ->
> /home/hieu/workspace/irstlm
> drwxr-xr-x  5 hieu hieu    4096 Mar 16 15:44 jam-files
> -rw-rw-r--  1 hieu hieu    6835 Apr 29 16:42 Jamroot
> -rw-r--r--  1 hieu hieu    5848 Mar  3 14:51 Jamroot~
> drwxrwxr-x  2 hieu hieu    4096 May 30 09:37 lib
> drwxr-xr-x  5 hieu hieu    4096 May  8 17:09 lm
> drwxr-xr-x  6 hieu hieu    4096 May 16 15:01 mert
> drwxr-xr-x  3 hieu hieu    4096 Mar 13 17:27 mingw
> drwxr-xr-x  4 hieu hieu    4096 May 16 14:26 mira
> drwxr-xr-x  5 hieu hieu    4096 Mar 12 19:27 misc
> drwxr-xr-x  7 hieu hieu   12288 May 20 19:52 moses
> drwxr-xr-x  3 hieu hieu    4096 May 20 19:52 moses-chart-cmd
> drwxr-xr-x  3 hieu hieu    4096 May  7 09:53 moses-cmd
> -rw-------  1 hieu hieu       0 May  1 10:24 nohup.out
> -rw-r--r--  1 hieu hieu     159 Jan 15 10:58 NOTICE
> drwxr-xr-x  3 hieu hieu    4096 Apr 17 19:13 OnDiskPt
> drwxr-xr-x  8 hieu hieu    4096 Mar 16 15:44 phrase-extract
> -rwxr-xr-x  1 hieu hieu     260 Jun  2 18:15 previous.sh
> lrwxrwxrwx  1 hieu hieu      36 Jan 22 16:08 probingPT ->
> /home/hieu/workspace/github/proj4.hh
> lrwxrwxrwx  1 hieu hieu      28 Jan 20 16:29 randlm ->
> /home/hieu/workspace/randlm/
> drwxr-xr-x  3 hieu hieu    4096 May 12 19:16 regression-testing
> drwxr-xr-x 16 hieu hieu    4096 Apr 29 16:42 scripts
> drwxr-xr-x  3 hieu hieu    4096 Apr 17 19:13 search
> lrwxrwxrwx  1 hieu hieu      26 Jan 20 16:23 srilm ->
> /home/hieu/workspace/srilm
> drwxr-xr-x  3 hieu hieu    4096 Jan 15 11:04 symal
> drwxr-xr-x  5 hieu hieu    4096 May  8 17:08 util
>
>
>
> On 3 June 2014 08:44, Lars Bungum <lars.bun...@idi.ntnu.no> wrote:
>
>> Hi,
>>
>> I try to import the Eclipse projects in the contrib/other-builds
>> directory, but I am having some problems.   Despite following the steps
>> exactly, the projects fail to build with this error message:
>>
>> /usr/bin/ld: cannot find -lmoses
>>
>> (and more for the other modules I didn't symlink in yet).  When I look
>> into the other-builds/moses directory, it is empty.    What do I have to
>> do to get this working?
>>
>> //LB
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>
>
>
> --
> Hieu Hoang
> Research Associate
> University of Edinburgh
> http://www.hoang.co.uk/hieu
>
>
>


-- 
Hieu Hoang
Research Associate
University of Edinburgh
http://www.hoang.co.uk/hieu
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to