Using cout in native function (JNI)

[fareeda]

hi,

I always get an exception "java.lang.UnsatisfiedLinkError" when I use
"cout" in my native function.
It works
- when i use "printf"
- other C++ features

Here is an example of the native C code I have:
---
#include <jni.h>
#include "FirstNative.h"
#include <iostream>
using namespace std;

JNIEXPORT void JNICALL Java_FirstNative_display(JNIEnv *env, jobject
obj)
{
cout << "Hello world!\n";
return;
}
---

Am I missing anything?
Regards
Fareeda

[fareeda]

Sorry for my earlier incorrect message but I am not able to work with
ANY C++ functionality. [I just had tried to use classes which worked].
I get the exception when using any c++ functions.

Any clue?

PS: I did make sure to add "extern C" in the header file, as per the
other discussions foudn on this topic.

Regards

[Raymond DeCampo]

fareeda wrote:

Sorry for my earlier incorrect message but I am not able to work with
ANY C++ functionality. [I just had tried to use classes which worked].
I get the exception when using any c++ functions.

Any clue?

PS: I did make sure to add "extern C" in the header file, as per the
other discussions foudn on this topic.

I would start by verifying that you can make a stand-alone C++
executable (no JNI involved). After that, create a library (same kind
as used by JNI) and verify that you can make a C++ executable that uses
the library. Then verify that you can make a C executable that uses the
library. That should shake out any environmental issues.

HTH,
Ray

[mhandis]

Also try moving #include <iosteam> to the top of the includes.
Occasionally they clash without causing compiler warnings.

fareeda wrote:

Sorry for my earlier incorrect message but I am not able to work with
ANY C++ functionality. [I just had tried to use classes which worked].
I get the exception when using any c++ functions.

Any clue?

PS: I did make sure to add "extern C" in the header file, as per the
other discussions foudn on this topic.

Regards

[fareeda]

Thanks for the information. But the following finally hellped me:
Using compiler options "-lCrun -lCstd" during creation of the library.
Also, these options have to be added AT THE END (else it does not work :()

Thanks
Fareeda