Just for the record, I tried this (running via deployCppService) on Windows:
- In addition to downloading/unzipping/setting up UIMACPP & building the
DaveDetector:
-- Download and unzip the UIMA-AS binary distribution, and set UIMA_HOME to
that
- Add UIMA_HOME/bin to the PATH
- Start a broker on localhost by typing startBroker in a new command window.
Leave it up and running.
- In a new command window, cd $UIMACPP_HOME/examples
- deployCppService descriptors/DaveDetector.xml DAVEDETECTOR
- copy $UIMA_HOME/examples/descriptors/as/MeetingDetectorAsyncAE.xml to
DaveDetector.xml in the same directory, edit
DaveDetector.xml to change MeetingDetectorTaeQueue ==> DAVEDETECTOR
- export UIMA_JVM_OPTS=-DdefaultBrokerURL=tcp://localhost:61616
from same directory as DaveDetector.xml: runAE.sh DaveDetector.xml ../../data
and it ran OK.
-Marshall
On 8/17/2012 12:19 PM, Eddie Epstein wrote:
>> [ ] +1 OK to release
>> [ ] 0 Don't care
>> [x ] -1 Not OK to release, because ...
> deployCppService from uimacpp-2.4.0-bin64.tgz fails on my test machine
> libssl.so.0.9.8 => not found
> libcrypto.so.0.9.8 => not found
>
> Using an SDK built from uimacpp-2.4.0-src.tgz, these two libs were found at
> libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003dc4e00000)
> libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x0000003dc3a00000)
>
> Are these lib dependencies necessary?
>
> Another serious problem is with the "make sdk" step: the default
> --prefix is set to /usr/local but "make sdk" assumes that the "make
> install" step has set --prefix=./usr/local (notice the . after the
> =). The situation is made worse by the fact that the "make sdk" step
> ignores any manual override of --prefix.
>
> What went well:
> -all other build steps on linux 64bit from source tarball
> -all testing using built SDK
> -all testing except deployCppServer from 64bit bin tarball
> -sampling of md5 and other checksums/signatures looked good.
>
> Eddie
>
