Help - Search - Members - Calendar
Full Version: Sun J2me Kvm Available
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
cortez
I've always wondered why Sun provides JVM's for WinCE while we still don't have a decent up-to-date Java runtime environment... so I downloaded the source code of their smallest available JVM, especially targeted to devices with limited memory, processing power etc. Just to see if it can be build for the Zaurus.

QUOTE
K virtual machine (KVM) is a Java virtual machine that provides the basis for the CLDC reference implementation (RI). K stands for "Kilobyte" virtual machine, referring to the small footprint of the platform. The K virtual machine is very small -- starting from approximately 70K in size.

So much for the bla bla, attached a version compiled for pdaXrom RC11+. I've only just been succesful in building the code, so give it a try and see for yourself if it works.

I guess you guys have to do the testing wink.gif

The virtual machine: Click to view attachment (untar)
The runtime classes: Click to view attachment (DON'T unzip!)
adf
QUOTE(cortez @ Nov 10 2005, 10:15 PM)
I've always wondered why Sun provides JVM's for WinCE while we still don't have a decent up-to-date Java runtime environment... so I downloaded the source code of their smallest available JVM, especially targeted to devices with limited memory, processing power etc. Just to see if it can be build for the Zaurus.

QUOTE
K virtual machine (KVM) is a Java virtual machine that provides the basis for the CLDC reference implementation (RI). K stands for "Kilobyte" virtual machine, referring to the small footprint of the platform. The K virtual machine is very small -- starting from approximately 70K in size.

So much for the bla bla, attached a version compiled for pdaXrom RC11+. I've only just been succesful in building the code, so give it a try and see for yourself if it works.

I guess you guys have to do the testing wink.gif

The virtual machine: Click to view attachment (untar)
The runtime classes: Click to view attachment (DON'T unzip!)
*


looking forward to it smile.gif
Java and kphone are both great additions, thanks

ANy hope of a firefox java plugin?
cortez
For J2ME there are currently two configurations:
The CLDC is meant to be used on Mobile Phones and entry level PDA's. It uses KVM as virtual machine. Well, it's *very* simple, but it can be done, I've proven that much wink.gif

The other J2ME configuration is the CDC, targeted at high-end PDA's, set-top boxes and embedded devices. The runtime Personal Profile for Zaurus can be downloaded here from the Sun site, is still an early access product, and is so for at least a few years now. Apart from that, it's build for the original Sharp (QT) ROM.

So, I'm currently in the process of (re)building the CDC JVM for pdaXrom. The building has been succesfully done, but it seems I have tweaked the code a bit to much blink.gif so some more work has to be done.

After that, the Foundation Profile (non-GUI) and the Personal Profile (GUI) have to be build. The Personal Profile has to be rebuild with X11 into mind. This seems to be a question of adjusting the building parameters somewhat. At least I hope so unsure.gif

adf: A browser plugin is part of the fullblown J2SE, so I guess the answer to your question is no sad.gif.

I hope these efforts are useful for others as much as they are learnful to me wink.gif That depends of course whether or not I will be able to post some nice IPK's here tongue.gif

Wish me luck!

cortez
adf
QUOTE(cortez @ Nov 12 2005, 12:11 AM)
For J2ME there are currently two configurations:
The CLDC is meant to be used on Mobile Phones and entry level PDA's. It uses KVM as virtual machine. Well, it's *very* simple, but it can be done, I've proven that much  wink.gif

The other J2ME configuration is the CDC, targeted at high-end PDA's, set-top boxes and embedded devices. The runtime Personal Profile for Zaurus can be downloaded here from the Sun site, is still an early access product, and is so for at least a few years now. Apart from that, it's build for the original Sharp (QT) ROM.

So, I'm currently in the process of (re)building the CDC JVM for pdaXrom. The building has been succesfully done, but it seems I have tweaked the code a bit to much blink.gif so some more work has to be done.

After that, the Foundation Profile (non-GUI) and the Personal Profile (GUI) have to be build. The Personal Profile has to be rebuild with X11 into mind. This seems to be a question of adjusting the building parameters somewhat. At least I hope so unsure.gif

adf: A browser plugin is part of the fullblown J2SE, so I guess the answer to your question is no sad.gif.

I hope these efforts are useful for others as much as they are learnful to me wink.gif That depends of course whether or not I will be able to post some nice IPK's here  tongue.gif

Wish me luck!

cortez
*



Good luck,
and... full konqueror from kde 3.4 (which is available for rc 10, at least) uses the machines jvm rather than a browser plugin, right? Any hope with kvm/konqueror?
smuelas
QUOTE(cortez @ Nov 12 2005, 12:11 AM)
So, I'm currently in the process of (re)building the CDC JVM for pdaXrom. The building has been succesfully done, but it seems I have tweaked the code a bit to much blink.gif so some more work has to be done.
..........
I hope these efforts are useful for others as much as they are learnful to me wink.gif That depends of course whether or not I will be able to post some nice IPK's here  tongue.gif

Wish me luck!

cortez
*


I haven't seen this thread before. I think that your job can be wonderful. Just, a few minutes before I was writing to someone in here asking him what is the strange story about Java.
Now, I see that you are doing it "the hard way". Up to yesterday that I changed my "qtopia-debian+xqt" to pdaXrom, I used without any problem the standard Java complete from Blackdown, so jdk-1.1.8 plus SwingZ.jar. I wrote some applications on the SL-6000 and compiled them, and after they runned wonderfully in my desktop with JDK-1.5. Also on the Zaurus.
I have tried to do the same with pdaXrom but it seems that there are changes in some libraries in relation to Debian ones. I am unable to run java with graphics or frames, windows...etc. There is a permanent "Segmentation Fault" message when I try it.
Wouldn't be easier for you to try to arrange the way for jdk-1.1.8 to be able to run on pdaxrom?
Note that the combination of this "old" version plus Swing gives you an almost complete java sdk, able to do almost everything you do today with the last versions. And it runs quite satisfactorily in Zauruses...
Anyway, thanks a lot for your effort. I have download your kvm and will try it.
smuelas
Chero
QUOTE(smuelas @ Nov 15 2005, 02:09 PM)
QUOTE(cortez @ Nov 12 2005, 12:11 AM)

So, I'm currently in the process of (re)building the CDC JVM for pdaXrom. The building has been succesfully done, but it seems I have tweaked the code a bit to much blink.gif so some more work has to be done.
..........
I hope these efforts are useful for others as much as they are learnful to me wink.gif That depends of course whether or not I will be able to post some nice IPK's here  tongue.gif

Wish me luck!

cortez
*


I haven't seen this thread before. I think that your job can be wonderful. Just, a few minutes before I was writing to someone in here asking him what is the strange story about Java.
Now, I see that you are doing it "the hard way". Up to yesterday that I changed my "qtopia-debian+xqt" to pdaXrom, I used without any problem the standard Java complete from Blackdown, so jdk-1.1.8 plus SwingZ.jar. I wrote some applications on the SL-6000 and compiled them, and after they runned wonderfully in my desktop with JDK-1.5. Also on the Zaurus.
I have tried to do the same with pdaXrom but it seems that there are changes in some libraries in relation to Debian ones. I am unable to run java with graphics or frames, windows...etc. There is a permanent "Segmentation Fault" message when I try it.
Wouldn't be easier for you to try to arrange the way for jdk-1.1.8 to be able to run on pdaxrom?
Note that the combination of this "old" version plus Swing gives you an almost complete java sdk, able to do almost everything you do today with the last versions. And it runs quite satisfactorily in Zauruses...
Anyway, thanks a lot for your effort. I have download your kvm and will try it.
smuelas
*



Just mentioning :
I have been running "jabp" on pdaXrom. I can't remember which java program I used. At the time (a few moons back) I was running rc10 and had "jamvm" and "jikes" installed from unstable feed, as well as java blackdown 1.3.1 from "Chris Double's radio weblog". It only worked with one of them, and I think I copied some files from one to the other. (I really should keep notes of what i'm doing, but most of the time I'm too lazy to do so. It's a good thing a lot is saved in these forums).

Chero.
cortez
adf: Maybe I'll try Konquerer later, but first I will concentrate on this "project". kvm wouldn't work anyway, because it lacks the graphical capability needed. Maybe JamVM+Classpath works, but that needs further investigation.

smuelas: I'm not going to put a lot of effort in trying to get a closed source thing like Blackdown to work.

There seems to be a general need for full Swing support. First step in trying to achieve that is rebuilding J2ME. It has to work, because the J2ME-JVM source was build before by Sun (the early access version) for Qt. What I'm trying to do here is to rebuild it for pdaXrom, using X11. It's just a matter of reconfiguration. Building J2SE-JVM seems not to be an option, simply because the source lacks support for arm-linux.

Main difference between J2ME and J2SE are in java.awt and the omission of javax.swing. I don't know if Swing can be build seperately for use in J2ME, but I will certainly give it a try!

So, back to work now. I'll keep you updated!
adf
tried jamvm.... no good, but since I have no real clue what i'm doing, the problem could very well be me.
Meanie
if you have a j2me running on pdaxrom, then you could add swing by adding SwingZ.jar and the extra files required by blackdown, ie additional-ipq-stuff.tar.gz and you also need libawt.so
haven't tried this yet because I don't have pdaxrom installed yet, but that's what I intend to try out once I have pdaxrom which hopefully will be soon.
smuelas
QUOTE(Meanie @ Nov 15 2005, 11:26 PM)
if you have a j2me running on pdaxrom, then you could add swing by adding SwingZ.jar and the extra files required by blackdown, ie additional-ipq-stuff.tar.gz and you also need libawt.so
haven't tried this yet because I don't have pdaxrom installed yet, but that's what I intend to try out once I have pdaxrom which hopefully will be soon.
*

Hi Meanie, Cortez
I have very good news (or perhaps, not so good...). A complete version of j2sdk-1.3.1 is running at the moment in my SL-6000. There is a package "ipk" with j2re-1.3.1 from blackdown. The only thing to do is to download and install it. My sugestion is to do it in /mnt/cf or sd as it is quite big. It comes with all the needed libraries. It will be installed in /mnt/cf/usr/local/j2sdk1.3.1, so add to your PATH the needed directory with:
export PATH=$PATH:/mnt/cf/usr/local/j2sdk1.3.1/bin (I know yu know how already but perhaps others don't)
and the REAL JVM is yours. I have found a known bug: when launching some application there is a message (long message) about the fons. But the application opens wonderfully.
I will continue this message in a few moments. I have to look at the URL where you can download the ipk.

smuelas
smuelas
I continue, sorry.
But before I want to thank Pgas for his help. My first contact with pdaXrom was the day before yesterday. I had some troubles and I put a message on this list. Pgas answered me and in a very few lines he solved all my problems, including Java. Grreat guy, Pgas!!

You can download jre from
http://www.double.co.nz/zaurus/blackdown-jdk_1.3.1_arm.ipk

The next point is to be able to compile *.java files in the Z. For doing that, you need to download the original j2sdk-1.3.1 from blackdown.org. There is no such thing for arm. You must do it for i386. It is a compressed tar package. Unpack it wherever you want. Then, find the file "tools.jar" and move or copy it to the zaurus. It should be included in your: /usr/local/j2re1.3.1/lib/ext/ . Nothing more.
Then, create 3 files in j2re1.3.1/bin with the names: "javac", "jar", and "appletviewer". Edit them. Only one line for each one. For "javac" write:
java sun.tools.javac.Main $1
For "jar", almost the same:
java sun.tools.jar.Main $1
and for "appletviewer", just write
java sun.applet.AppletViewer $1
and that's all. If you have stablished your PATH you can compile your *.java files with javac. You can create java-packages with jar and launch and view your applets with appletviewer. Nice, isn't it..
Sorry, I forgot. Don't forgat to make your scripts executables with:
chmod +x javac
and so on.

smuelas
Meanie
QUOTE(smuelas @ Nov 17 2005, 12:37 AM)
I continue, sorry.
But before I want to thank Pgas for his help. My first contact with pdaXrom was the day before yesterday. I had some troubles and I put a message on this list. Pgas answered me and in a very few lines he solved all my problems, including Java. Grreat guy, Pgas!!

You can download jre from
http://www.double.co.nz/zaurus/blackdown-jdk_1.3.1_arm.ipk

The next point is to be able to compile *.java files in the Z. For doing that, you need to download the original j2sdk-1.3.1 from blackdown.org. There is no such thing for arm. You must do it for i386. It is a compressed tar package. Unpack it wherever you want. Then, find the file "tools.jar" and move or copy it to the zaurus. It should be included in your:  /usr/local/j2re1.3.1/lib/ext/  . Nothing more.
Then, create 3 files in j2re1.3.1/bin with the names: "javac", "jar", and "appletviewer". Edit them.  Only one line for each one. For "javac" write:
java sun.tools.javac.Main $1
For "jar", almost the same:
java sun.tools.jar.Main $1
and for "appletviewer", just write
java sun.applet.AppletViewer $1
and that's all. If you have stablished your PATH you can compile your *.java files with javac. You can create java-packages with jar and launch and view your applets with appletviewer. Nice, isn't it..
Sorry, I forgot. Don't forgat to make your scripts executables with:
chmod +x javac
and so on.

smuelas
*


You can get rid of the annoying font messages by editing font.properties and commenting out all the lines containing adobe.
smuelas
QUOTE(Meanie @ Nov 16 2005, 11:51 PM)
You can get rid of the annoying font messages by editing font.properties and commenting out all the lines containing adobe.
*


Thanks Meanie. Already done!
Apart from that, I'm testing the difference between the combination jdk118+swingZ.jar and the all new j2se131, and I'm not very satisfied.
The problem, in my very humble opinion, is that "tools.jar" is a huge thing. For compiling anything, it takes quite a lot of time and it's not precisely a thunder at running time.
It is necessary to be much more precise at programming time. For example, in my laptop, if I'm using swing, I write at the beginning:
import javax.swing.*;
and then, when needed, I write something like:
JPanel myPanel = new JPanel();
All that due to the fact that I don't use any kind of Eclipse or JBorland or Netbeans...

If used in the zaurus, it is very important to write the whole path everytime, and only import what will be used. For the example above, it would be:

import javax.swing.JPanel;
.....................................
javax.swing.Jpanel myPanel = new javax.swing.JPanel();

Anyway, the combination jdk118+swingZ.jar works quicker and better.

What do you think if we do (between you and myself and any other that would want) a new distribution of a serious, complete JDK for Zauruses?
My idea is to have something like Personal Java but bigger and with a complete AWT and the most used Swing and Java2. There are a lot of classes that are not used almost never. So, one aspect would be to remove everything unnecesary.
You have done already something very similar, so your work could be the start-up to begin with.
My personal interest is "profesional educational scientific programming" (it sounds impressive!!). So, Kopi, for example, but also Jikes, do not compile o.k. if using intensive float operations with double numbers, parsing text to double and all that stuff.
Another point is the "slowness" of zauruses in moving screen-pixels. So, I'm afraid that a part of the software should be done using the primitives for the framebuffer and/or the X's. Surely, those great guys from pdaXrom would be an enormous help.

I look forward to your ideas about all that.

smuelas
sashz
Hello

i compiled midp2 kvm for zaurus. Only ssl stuff unsupported because sun excluded it from source pack. Also i fixed bug in Xserver for 16 bits chars (need was fix it before sad.gif ).
If you like it i will upload for your testing.

screens attached smile.gif
plcg
QUOTE(sashz @ Nov 17 2005, 04:31 PM)
Hello

i compiled midp2 kvm for zaurus. Only ssl stuff unsupported because sun excluded it from source pack. Also i fixed bug in Xserver for 16 bits chars (need was fix it before sad.gif ).
If you like it i will upload for your testing.

screens attached smile.gif
*

Hello sashz,

I would like to test midp2 kvm.
Can you upload it, please ?

Thanks,
plcg
Meanie
QUOTE(smuelas @ Nov 18 2005, 12:31 AM)
QUOTE(Meanie @ Nov 16 2005, 11:51 PM)

You can get rid of the annoying font messages by editing font.properties and commenting out all the lines containing adobe.
*


Thanks Meanie. Already done!
Apart from that, I'm testing the difference between the combination jdk118+swingZ.jar and the all new j2se131, and I'm not very satisfied.
The problem, in my very humble opinion, is that "tools.jar" is a huge thing. For compiling anything, it takes quite a lot of time and it's not precisely a thunder at running time.
It is necessary to be much more precise at programming time. For example, in my laptop, if I'm using swing, I write at the beginning:
import javax.swing.*;
and then, when needed, I write something like:
JPanel myPanel = new JPanel();
All that due to the fact that I don't use any kind of Eclipse or JBorland or Netbeans...

If used in the zaurus, it is very important to write the whole path everytime, and only import what will be used. For the example above, it would be:

import javax.swing.JPanel;
.....................................
javax.swing.Jpanel myPanel = new javax.swing.JPanel();

Anyway, the combination jdk118+swingZ.jar works quicker and better.

What do you think if we do (between you and myself and any other that would want) a new distribution of a serious, complete JDK for Zauruses?
My idea is to have something like Personal Java but bigger and with a complete AWT and the most used Swing and Java2. There are a lot of classes that are not used almost never. So, one aspect would be to remove everything unnecesary.
You have done already something very similar, so your work could be the start-up to begin with.
My personal interest is "profesional educational scientific programming" (it sounds impressive!!). So, Kopi, for example, but also Jikes, do not compile o.k. if using intensive float operations with double numbers, parsing text to double and all that stuff.
Another point is the "slowness" of zauruses in moving screen-pixels. So, I'm afraid that a part of the software should be done using the primitives for the framebuffer and/or the X's. Surely, those great guys from pdaXrom would be an enormous help.

I look forward to your ideas about all that.

smuelas
*



yeah kopi and jikes compilers are smaller and faster but the compiled code lack precision when crunching numbers.

unfortunately, bundling java with less classes would violate the java license, so its either full bloated j2se (with all APIs implemented, ie all the classes) or reduced j2me API (which does not have swing and awt). That's why it doesnt all come prepackaged together for you and why you have to puzzle it together yourself sad.gif
adf
QUOTE(Meanie @ Nov 17 2005, 11:59 PM)
QUOTE(smuelas @ Nov 18 2005, 12:31 AM)
QUOTE(Meanie @ Nov 16 2005, 11:51 PM)

You can get rid of the annoying font messages by editing font.properties and commenting out all the lines containing adobe.
*


Thanks Meanie. Already done!
Apart from that, I'm testing the difference between the combination jdk118+swingZ.jar and the all new j2se131, and I'm not very satisfied.
The problem, in my very humble opinion, is that "tools.jar" is a huge thing. For compiling anything, it takes quite a lot of time and it's not precisely a thunder at running time.
It is necessary to be much more precise at programming time. For example, in my laptop, if I'm using swing, I write at the beginning:
import javax.swing.*;
and then, when needed, I write something like:
JPanel myPanel = new JPanel();
All that due to the fact that I don't use any kind of Eclipse or JBorland or Netbeans...

If used in the zaurus, it is very important to write the whole path everytime, and only import what will be used. For the example above, it would be:

import javax.swing.JPanel;
.....................................
javax.swing.Jpanel myPanel = new javax.swing.JPanel();

Anyway, the combination jdk118+swingZ.jar works quicker and better.

What do you think if we do (between you and myself and any other that would want) a new distribution of a serious, complete JDK for Zauruses?
My idea is to have something like Personal Java but bigger and with a complete AWT and the most used Swing and Java2. There are a lot of classes that are not used almost never. So, one aspect would be to remove everything unnecesary.
You have done already something very similar, so your work could be the start-up to begin with.
My personal interest is "profesional educational scientific programming" (it sounds impressive!!). So, Kopi, for example, but also Jikes, do not compile o.k. if using intensive float operations with double numbers, parsing text to double and all that stuff.
Another point is the "slowness" of zauruses in moving screen-pixels. So, I'm afraid that a part of the software should be done using the primitives for the framebuffer and/or the X's. Surely, those great guys from pdaXrom would be an enormous help.

I look forward to your ideas about all that.

smuelas
*



yeah kopi and jikes compilers are smaller and faster but the compiled code lack precision when crunching numbers.

unfortunately, bundling java with less classes would violate the java license, so its either full bloated j2se (with all APIs implemented, ie all the classes) or reduced j2me API (which does not have swing and awt). That's why it doesnt all come prepackaged together for you and why you have to puzzle it together yourself sad.gif
*




If you don't mind .02 usd from someone with no useful knowledge... maybe the full j2se would be a good choice? Storage gets cheaper by the minute and embedded devices get faster by the season. If it worked useably, I think you'd see a lot of enthusiasm for it among us end-user types smile.gif and it would be a development path that would make next gen devices better rather than forcing the a reinvention of the wheel.
smuelas
QUOTE
yeah kopi and jikes compilers are smaller and faster but the compiled code lack precision when crunching numbers.

unfortunately, bundling java with less classes would violate the java license, so its either full bloated j2se (with all APIs implemented, ie all the classes) or reduced j2me API (which does not have swing and awt). That's why it doesnt all come prepackaged together for you and why you have to puzzle it together yourself sad.gif
*


I see... Well, perhaps Sun would be happy to accept something well done...

Anyway, I am trying now the "old" combination (jdk118+swingZ.jar) in an environement of (pdaXrom+Debian) where Debian is used only for "rare" applications not found in pdaXrom AND Java and "chrooting" only for launching the applications. (This is done according to instructions on this list). The combination is incredible, very, very good, (thanks Pgas), and now my quite big Java applications that I have tested work at a reasonably speed, and I can write, compile and run everything without leaving the 6000.
BTW, I have modified the files for the keyboard and now the absurdity of the "tab+Caps_Lock" is finished. I have also implemented the signs: { } [ ] \ ^ The right-Shift is the new Caps_Lock, and Tab is only Tab.

smuelas
plcg
QUOTE(plcg @ Nov 17 2005, 09:52 PM)
QUOTE(sashz @ Nov 17 2005, 04:31 PM)
Hello

i compiled midp2 kvm for zaurus. Only ssl stuff unsupported because sun excluded it from source pack. Also i fixed bug in Xserver for 16 bits chars (need was fix it before sad.gif ).
If you like it i will upload for your testing.

screens attached smile.gif
*

Hello sashz,

I would like to test midp2 kvm.
Can you upload it, please ?

Thanks,
plcg
*


Hello,

No news about midp2 ? unsure.gif

plcg
Fatty
QUOTE(smuelas @ Nov 16 2005, 10:37 PM)
I continue, sorry.
But before I want to thank Pgas for his help. My first contact with pdaXrom was the day before yesterday. I had some troubles and I put a message on this list. Pgas answered me and in a very few lines he solved all my problems, including Java. Grreat guy, Pgas!!

You can download jre from
http://www.double.co.nz/zaurus/blackdown-jdk_1.3.1_arm.ipk

The next point is to be able to compile *.java files in the Z. For doing that, you need to download the original j2sdk-1.3.1 from blackdown.org. There is no such thing for arm. You must do it for i386. It is a compressed tar package. Unpack it wherever you want. Then, find the file "tools.jar" and move or copy it to the zaurus. It should be included in your:  /usr/local/j2re1.3.1/lib/ext/  . Nothing more.
Then, create 3 files in j2re1.3.1/bin with the names: "javac", "jar", and "appletviewer". Edit them.  Only one line for each one. For "javac" write:
java sun.tools.javac.Main $1
For "jar", almost the same:
java sun.tools.jar.Main $1
and for "appletviewer", just write
java sun.applet.AppletViewer $1
and that's all. If you have stablished your PATH you can compile your *.java files with javac. You can create java-packages with jar and launch and view your applets with appletviewer. Nice, isn't it..
Sorry, I forgot. Don't forgat to make your scripts executables with:
chmod +x javac
and so on.

smuelas
*


I installed blackdown and followed the instructions to create 'javac' tool and it works fine at first, able to compile a little java program with swing. But after I reboot the Z, when I run javac again I get

"error while loading shared libraries: libBrokenLocale.so.1: cannot open shared object file: No such file or directory"

But I didn't do anything else before reboot. Any clue?
Meanie
QUOTE(Fatty @ Nov 24 2005, 05:32 AM)
QUOTE(smuelas @ Nov 16 2005, 10:37 PM)
I continue, sorry.
But before I want to thank Pgas for his help. My first contact with pdaXrom was the day before yesterday. I had some troubles and I put a message on this list. Pgas answered me and in a very few lines he solved all my problems, including Java. Grreat guy, Pgas!!

You can download jre from
http://www.double.co.nz/zaurus/blackdown-jdk_1.3.1_arm.ipk

The next point is to be able to compile *.java files in the Z. For doing that, you need to download the original j2sdk-1.3.1 from blackdown.org. There is no such thing for arm. You must do it for i386. It is a compressed tar package. Unpack it wherever you want. Then, find the file "tools.jar" and move or copy it to the zaurus. It should be included in your:  /usr/local/j2re1.3.1/lib/ext/  . Nothing more.
Then, create 3 files in j2re1.3.1/bin with the names: "javac", "jar", and "appletviewer". Edit them.  Only one line for each one. For "javac" write:
java sun.tools.javac.Main $1
For "jar", almost the same:
java sun.tools.jar.Main $1
and for "appletviewer", just write
java sun.applet.AppletViewer $1
and that's all. If you have stablished your PATH you can compile your *.java files with javac. You can create java-packages with jar and launch and view your applets with appletviewer. Nice, isn't it..
Sorry, I forgot. Don't forgat to make your scripts executables with:
chmod +x javac
and so on.

smuelas
*


I installed blackdown and followed the instructions to create 'javac' tool and it works fine at first, able to compile a little java program with swing. But after I reboot the Z, when I run javac again I get

"error while loading shared libraries: libBrokenLocale.so.1: cannot open shared object file: No such file or directory"

But I didn't do anything else before reboot. Any clue?
*



run ldconfig
smuelas
QUOTE(Meanie @ Nov 23 2005, 11:42 PM)
QUOTE(Fatty @ Nov 24 2005, 05:32 AM)

I installed blackdown and followed the instructions to create 'javac' tool and it works fine at first, able to compile a little java program with swing. But after I reboot the Z, when I run javac again I get

"error while loading shared libraries: libBrokenLocale.so.1: cannot open shared object file: No such file or directory"

But I didn't do anything else before reboot. Any clue?
*


run ldconfig
*



BTW, this is a problem not only with Java but also with other applications. I have included "ldconfig" in some of the init scripts of /etc/rc.d/init.d/. (I don't remember at this moment which one). I recommend to do it before launching the X's when rebooting the Zaurus.
smuelas
Fatty
QUOTE(smuelas @ Nov 24 2005, 03:08 PM)
QUOTE(Meanie @ Nov 23 2005, 11:42 PM)
QUOTE(Fatty @ Nov 24 2005, 05:32 AM)

I installed blackdown and followed the instructions to create 'javac' tool and it works fine at first, able to compile a little java program with swing. But after I reboot the Z, when I run javac again I get

"error while loading shared libraries: libBrokenLocale.so.1: cannot open shared object file: No such file or directory"

But I didn't do anything else before reboot. Any clue?
*


run ldconfig
*



BTW, this is a problem not only with Java but also with other applications. I have included "ldconfig" in some of the init scripts of /etc/rc.d/init.d/. (I don't remember at this moment which one). I recommend to do it before launching the X's when rebooting the Zaurus.
smuelas
*



Thank you so much. It works now.
cortez
Just to keep you updated, a new VM is coming up, after the smallest of VM's (KVM) I'm getting close to getting CVM working.

Edited:
I'm still wrestling to get this working. The KVM with Foundation and Personal profile is working, but I'm tweakin' the Makefiles to get AWT and Swing support for X11 working. I'm almost there... blink.gif
anunakin
QUOTE(cortez @ Nov 27 2005, 12:04 PM)
Just to keep you updated, a new VM is coming up, after the smallest of VM's (KVM) I'm getting close to getting CVM working.

Edited:
I'm still wrestling to get this working. The KVM with Foundation and Personal profile is working, but I'm tweakin' the Makefiles to get AWT and Swing support for X11 working.    I'm almost there... blink.gif
*


Any hope to have a MIDP 2 ipk ?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.