Re: Use Dom's new link-grammar module.

Ryan Pavlik wrote:

>
> Martin Sevior wrote:
>
>> CVS:
>> ----------------------------------------------------------------------
>> CVS: Enter Log. Lines beginning with `CVS:' are removed automatically
>> CVS:
>> CVS: Committing in .
>> CVS:
>> CVS: Modified Files:
>> CVS: linkgrammarwrap/LinkGrammarWrap.cpp
>> CVS:
>> ----------------------------------------------------------------------
>> Small changes needed to use use Dom's english version of link-grammar.
>>
>> So now the new link-grammar module in the abiword cvs repository works
>> with the grammar checking plugin.
>>
>> Simply cvs co link-grammar
>> ./autogen.sh
>> ./configure --prefix=/Same/place/as/your/abiword/build/prefix
>> make
>> make install
>>
>> Then build the abigrammar plugin.
>>
>> Have fun!
>>
>> See the latest screen shot with the square blue squiggles.
>>
>> http://www.ph.unimelb.edu.au/~msevior/abiword/link-abi.png
>>
>> Cheers
>>
>> Martin
>>
>>
> Presuming you don't set a prefix on Windows, how is this done? I
> recall Dom mentioning there was a DLL compile...
>
When attempting to build this on Windows, I get this result (MSYS/MingW)
Administrator@QUENYA /d/src/abiroot/link-grammar
$ ./autogen.sh
automake (GNU automake) 1.8.2
You should add the contents of `/usr/share/aclocal/libtool.m4' to
`aclocal.m4'.
Creating aclocal.m4: aclocal -I /d/GTK/share/aclocal -I
/local/share/aclocal
automake --add-missing --copy --foreign

* * * warning: possible errors while running automake - check autogen.err

Creating configure...

You can run ./configure now.

Administrator@QUENYA /d/src/abiroot/link-grammar
$ ./configure
./configure: line 1263: syntax error near unexpected token
`AM_INIT_AUTOMAKE($PACKAGE,'
./configure: line 1263: `AM_INIT_AUTOMAKE($PACKAGE, $VERSION)'

Administrator@QUENYA /d/src/abiroot/link-grammar
$

My autogen.err file:
aclocal: couldn't open directory `/d/GTK/share/aclocal': No such file or
directory
configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal).
link-grammar/Makefile.am:1: OS_WIN32 does not appear in AM_CONDITIONAL
link-grammar/Makefile.am:5: OS_WIN32 does not appear in AM_CONDITIONAL
link-grammar/Makefile.am:21: Libtool library used but `LIBTOOL' is undefined
link-grammar/Makefile.am:21:
link-grammar/Makefile.am:21: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
link-grammar/Makefile.am:21: to `configure.in' and run `aclocal' and
`autoconf' again.
/usr/share/automake-1.8/am/depend2.am: am__fastdepCC does not appear in
AM_CONDITIONAL
/usr/share/automake-1.8/am/depend2.am: AMDEP does not appear in
AM_CONDITIONAL

It is interesting to note that I was able to ./configure, make, and make
install the tarball previously posted here, though I got no further in
building the plugin, since there weren't any "Makefile"s and those that
I made (without any prior experience) weren't linking in the
link-grammar files I had compiled.

Thanks for any help! I can't wait till I can see blocky green or blue
lines under sentences likes this ones!

-- 
Ryan Pavlik
--
"Forget injuries, never forget kindnesses."  --Confucius