[
https://issues.apache.org/jira/browse/UIMA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470371
]
Eddie Epstein commented on UIMA-260:
------------------------------------
Looks like this issue goes beyond integration of C++ analytics into an eclipse
working environment. Many of the run_configuration files also setup logging
with a VM argument:
"-Djava.util.logging.config.file=${env_var:UIMA_HOME}/config/Logger.properties"
So eclipse was already dependent on the external environment to have UIMA_HOME
set. Unless we want to change how logging and other VM arguments get set, no
reason to change this for C++ either. Marshall suggested just adding
documentation on how to setup UIMA_HOME on MacOSX.
Longer term the eclipse dependency on the external environment for where UIMA
is installed should probably be fixed, perhaps as Marshall has also suggested,
by running an eclipse configuration fixup script.
> Set env vars in setUimaClasspath and the Eclipser run configs
> -------------------------------------------------------------
>
> Key: UIMA-260
> URL: https://issues.apache.org/jira/browse/UIMA-260
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test, Examples
> Reporter: Adam Lally
> Assigned To: Adam Lally
> Fix For: 2.1
>
>
> To support runnin C++ annotators out-of-the-box, need to set environment vars
> in setUimaClasspath and our Eclipse run configs.
> To account for Windows, *nix, and Mac we actually need to set three
> variables: PATH, LD_LIBRARY_PATH, and DYLD_LIBRARY_PATH.
> To PATH we'd append
> %UIMA_HOME%/uimacpp/bin:%UIMA_HOME%/uimacpp/examples/tutorial/src
> To the latter two we'd append
> $UIMA_HOME/uimacpp/lib:$UIMA_HOME/uimacpp/examples/tutorial/src
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
