2012/3/26 Stephen Tigner <[email protected]>
> On Sun, Mar 25, 2012 at 10:49 AM, Jacob Nordfalk
> <[email protected]> wrote:
>
> > Its not that clear from the code diff, but the idea is first to look for
> the
> > commands in the installation dir, then on the general PATH:
> >
> > PATH="${APERTIUM_PATH}:${PATH}"
> >
> >
> > I think the java port should do the same, but first check if the task
> can be
> > done by lttoolbox-java itself internally. So, like
> >
> > PATH="can we do it without invoking external
> > stuff?:${APERTIUM_PATH}:${PATH}"
> >
> > :-)
>
> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable?
Sorry, it wasnt clear (again - Unhammer, your'e fired as ghost writer :-).
APERTIUM_PATH would be the path to the 'apertium binary'
In shell language it would be expressed as
APERTIUM_PATH="$(dirname $0)"
this makes sure that binaries are first searched for in the same directory
as the 'apertium' command.
--
Jacob Nordfalk <https://plus.google.com/114820443085046080944>
http://javabog.dk
Android-udvikler og underviser på
IHK<http://cv.ihk.dk/diplomuddannelser/itd/vf/MAU>og
Lund&Bendsen <https://www.lundogbendsen.dk/undervisning/beskrivelse/LB1809/>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
