On Wed, May 22, 2013 at 3:54 PM, m...@rpzdesign.com wrote:
> Watch out when the Intel mobile processors come along, I doubt they will be
> ARM 7 compatible.
> But they may be x86!
That's not problem. If we have x86 too, then instead of doing 2 clicks
to build the project, I'll have to do 4 clicks
Felipe:
Any comments on how you would mix C and pascal into the same binary
for JNI/Android?
I have some encryption routines in C that I need to link to Pascal and
then get called by Java.
md
On 5/22/2013 7:29 AM, Felipe Monteiro de Carvalho wrote:
Hello,
On Wed, May 22, 2013 at 1:50 PM, m
You sir,
Are a good man.
Thx for the link.
Watch out when the Intel mobile processors come along, I doubt they will
be ARM 7 compatible.
But they may be x86!
md
On 5/22/2013 7:29 AM, Felipe Monteiro de Carvalho wrote:
Hello,
On Wed, May 22, 2013 at 1:50 PM, m...@rpzdesign.com wrote:
Ar
Hello,
On Wed, May 22, 2013 at 1:50 PM, m...@rpzdesign.com wrote:
> Are you saying that you are writing JNI routines in Pascal for android?
Yes. And luckly it works in all devices =) I was a bit scared that I
might hit a wierd problem here involving code generation or whatever,
but ... just a no
On 2013-05-22 13:50, m...@rpzdesign.com wrote:
Are you saying that you are writing JNI routines in Pascal for android?
If so, can you post some of the things like the pascal header files
you use to allow for the creation of the .so files
so that Java can call into pascal across the JNI interfa
Are you saying that you are writing JNI routines in Pascal for android?
If so, can you post some of the things like the pascal header files you
use to allow for the creation of the .so files
so that Java can call into pascal across the JNI interface.
I have 2 projects that I need Pascal talkin
Am 21.05.2013 20:52, schrieb Felipe Monteiro de Carvalho:
Oh, forget it. Someone answered in android-ndk group: I had a typo in
another JNI routine which caused the problem.
It seams that the new Android checks all JNI routines at startup.
Older ones checked the routines only when they were util
Oh, forget it. Someone answered in android-ndk group: I had a typo in
another JNI routine which caused the problem.
It seams that the new Android checks all JNI routines at startup.
Older ones checked the routines only when they were utilized, so would
only crash when it was utilized.
--
Felipe
On Tue, May 21, 2013 at 5:47 PM, Felipe Monteiro de Carvalho
wrote:
> My only idea at the moment is to do the static export too... maybe
> that will work, lets see.
No, that didn't help anything =(
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillis
