[
https://issues.apache.org/jira/browse/UIMA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein reopened UIMA-260:
--------------------------------
The implemented code sets the eclipse launch configuration environment as so:
${env_var:UIMA_HOME}/uimacpp/lib: ...etc
This is a problem, as it requires the environment used to Launch eclipse to
have the right env value for UIMA_HOME. It is inflexible and awkwards to change
the environment for applications like eclipse which are launched graphically.
Better is to create a new eclipse "String Substitution" variable named
UIMA_HOME from the preferences->Run/Debug menu, and change the launch
configuration to be:
${UIMA_HOME}/uimacpp/lib: ...etc
This is still not ideal, as the location of UIMA_HOME needs to be set both here
and in the CLASSPATH variable, but it seems there is no way for a single
eclipse variable to be used in both the build classpath and the environment
setup.
Eddie
> 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.
