uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie Epstein" <eaepst...@gmail.com>
Subject Re: Mixing C++ and Java annotators
Date Fri, 04 Apr 2008 11:19:03 GMT
The story with Windows release vs debug builds is a bit complicated by the
fact that they use different new/free code. Objects created in debug code
cannot be freed in release code and visa versa.

buildSDK adds both release (uima.dll) and debug (uimaD.dll) versions of the
DLL. The sample VC projects link the appropriate version. When loading the
annotator, the debug version of uimacpp will append 'D' to the
annotatorImplementationName from the uima component descriptor.

By default the JVM will use uima.dll when calling a uimacpp annotator. To
use a debug annotator from Java, specify -DDEBUG_UIMACPP when starting the

There are also two versions of the native driver, runAECpp.exe and
runAECppD.exe to match the annotator build, as well as two versions of the
native service wrapper, deployCppService.exe and deployCppServiceD.exe.

Glad to hear things are working for you,

On Thu, Apr 3, 2008 at 11:09 PM, Johansson, Justin (Contractor) <
Justin.Johansson@dsto.defence.gov.au> wrote:

> Thanks Eddie for that.
> I've just done two things and the problem has gone away so which of the
> two things fixed the problem I do not yet know.
> 1. Checked out latest UIMACPP from Apache SVN and build the binaries.
> The last version I had was about 2 months old.
> 2. Pointed the paths to the Release version as opposed to the Debug
> version of the bin.
> All's well after doing both of those things.
> I was about to go through "Verifying Your Installation" prior to this
> but now no need to.
> Is there an issue with using Debug binaries as opposed to Release?  If
> so how does one configure for Debug binaries?
> BTW.  I'm using Visual Studio 2005.
> Thanks
> Justin

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message