krok55 / perldroid

Automatically exported from code.google.com/p/perldroid
0 stars 0 forks source link

How does perldroid compare to the Perl support in Android-scripting? #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Please see http://code.google.com/p/android-scripting/issues/detail?id=32

Original issue reported on code.google.com by ddascale...@gmail.com on 7 Jan 2010 at 10:55

GoogleCodeExporter commented 9 years ago
Sorry I haven't seen this entry...
I'm working very seldomely, for the moment, on this project.

Well my project aims to supports all of Perl on all of Android. For the moment 
it is
only a kind of proof of concept. AFAIK, android-scripting restrict the 
environment so
you should not be able to implement all of what you can do in Java in Perl. But 
I
don't know every bit of android-scripting so I can't be sure. E.g. I don't know 
how
android-scripting deals with permissions. On my system I use normal Android
permissions and every application is installed as a normal application, in a 
.apk.

Another thing is that I get a lot of fun working on this and I learn about perl
internals and JNI :-p

For the moment I'm able to install one PerlDroid application on a phone (>=1.6),
generate another application in Perl and install / run it.

Any question / remark is welcome...

Original comment by feckmicr...@gmail.com on 5 Apr 2010 at 4:16

GoogleCodeExporter commented 9 years ago
BTW I took a look on the Perl part in ASE project and it seems that they are 
working
on the possibility to install scripts as .apk. This can solve the issue of
permissions I was talking about. OTOTH I managed to build my perl lib using
exclusively Android-SDK and Android-NDK (i.e. not using Android source), which 
is
more convenient. But there are some tricks I had to use because the managing of
already built libraries in Android.mk of the NDK is missing. Also, to build the
libperl.so I used another trick in the makefile, because it is almost 
impossible to
build it with the makefiles provided. So I have my own that downloads the 
source of
Perl 5.10.0, patches it and builds it.

Also it is important to note that they have to implement every Android framework
feature in facade, and they have some feature requests in their issue tracker, a
problem that my project avoids.

But again, PerlDroid is still a proff of concept, I don't have much time to 
work on
it (would be great if Google took a look at it :-p).

Original comment by feckmicr...@gmail.com on 5 Apr 2010 at 8:18

GoogleCodeExporter commented 9 years ago
Finally I won't implement Java bindings.

I'm working with the [http://code.google.com/p/perl-android-apk/ 
perl-android-apk] project to provide them with a working perl interpreter. 
Maybe SL4A will want to use it, too.

I'm also wanting to extend this project to use the perl-android-apk's project 
idea but without including the interpreter in the APK, some sort or mix between 
SL4A and perl-android-apk.

Original comment by feckmicr...@gmail.com on 26 Jun 2012 at 4:46