Developers Kit

On AmiUpdate you can find an update consisting of a few developer's files. There's a new Java compiler, a simple example, as well as documentation.

Just update your system, go to JAmiga:Documents/Developer.guide, and you're just minutes away from compiling your own applications.

I'll try to add more info on how you can use it with various third-party jar files.

@jaokim
You rock!

@jaokim

Wow, thanks a lot

Installed over amiupdate, have a go for simple test cases: works. Cool !

@jaokim

Trying to compile HelloWorld.java using the instructions I got: "java.lang.ClassNotFoundException: org/eclipse/jdt/internal/compiler/batch/Main".

@Joakim

Here i got
10.Amiga OS 4:System/JAmiga/Examples> list
HelloWorld.java 596 ----rw-d 09-Déc-13 22:27:12
1 fichier - 596 octets - 2 blocs utilisés

10.Amiga OS 4:System/JAmiga/Examples> jamiga:javac Helloworld.java
Starting compiler...
Exception occurred while VM initialising.
java/lang/NoClassDefFoundError: jamvm/java/lang/VMClassLoaderData
Done!
10.Amiga OS 4:System/JAmiga/Examples> list
HelloWorld.java 596 ----rw-d 09-Déc-13 22:27:12
1 fichier - 596 octets - 2 blocs utilisés

@TSK & JosDuchIt:

Hmm. Perhaps something is wrong with your CLASSPATH ENV-variable.

There are a few things needed in order to make it work:
1. The "CURRDIR:" assign needs to be in the CLASSPATH ENV variable.
2. The CLASSPATH ENV variable must be in uppercase. Even if the Amiga command getenv ignores the case, the internal getenv used by JamVM doesn't.

I tried to make my AutoInstall script fix these issues, even if you had your own CLASSPATH set.

So, please check these things:

<b>1. Check uppercase CLASSPATH ENV</b>
In CLI do:
<code> dir ENV:classpat#?</code>, and
<code> dir ENVARC:classpat#?</code>

Both should return CLASSPATH in uppercase:
<code> CLASSPATH</code>

If its in lowercase, please rename the files (or delete them both, and do the setenv thing below.)


<b>2. Check CURRDIR in CLASSPATH ENV</b>
In CLI do:
<code> getenv CLASSPATH</code>

It should return something like
<code> CURRDIR:,</code>
or, CURRDIR: followed by your previous settings
<code> CURRDIR:,JAmiga:,Work:blabla/,[other drawers you might have added]</code>

If it doesn't have CURRDIR:, please set the CLASSPATH ENV to "CURRDIR:," (or add it to the beginning of whatever you have).

<code> setenv SAVE CLASSPATH CURRDIR:</code>, or

<code> setenv SAVE CLASSPATH CURRDIR:,JAmiga:,Work:blabla/,[other drawers you might have added]</code>


If that doesn't solve it, please double-click JAmiga:JAmiga, and paste the output here.


You might also try running the ECJ compiler on its own (if you look in the JAmiga:javac script file, this is basically what is done):
<code> jamiga:jamvm -jar JAmiga:lib/ecj-4.3.jar</code>
This should give some version info and help. If it doesn't something is very wrong.

Hmm... again.
Quote:
Could it be the space in the drive name...?

I'm not at my miggy currently, so I can't try it. But that could be one possible reason for failure.

It might in that case work if you explicitly tell javac where the source file is:

<code>jamiga:javac jamiga:examples/HelloWorld.java</code>

@jaokim

CLASSPATH env var is fully in capital letters and contains: CURRDIR:,

No spaces in the volume name or path.

Btw. I don't have any eclipse directory in classpath/share/classpath/org or any other similar directory. Do that matter ?

The output of double clicking the JAmiga icon:

== This is JAmiga - Java for AmigaOS 4 ==
This script will give you information on all installed
parts of JAmiga.
When reporting errors this information should be included.

[JAmiga release version]
JAmiga 1.2 (15.8.13)
"JAmiga release version"

[JamVM version]
jamvm 1.4 (2.11.13)
AmigaOS 4 build of jamvm 1.5.4
java version "1.5.0"
JamVM version 1.5.4
Copyright (C) 2003-2012 Robert Lougher <rob@jamvm.org.uk>

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2,
or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

Build information:

Execution Engine: switch-based interpreter
Compiled with: gcc 4.2.4 (adtools build 20090118)

Boot Library Path: JAmiga:classpath/lib/classpath
Boot Class Path: JAmiga:jvm/share/jamvm/classes,JAmiga:classpath/share/classpath

[JAmiga native libraries version]
JAmiga:classpath/lib/classpath/gnuclasspath.library: gnuclasspath.library 0.1
JAmiga:classpath/lib/classpath/jamint.library: jamint.library 1.0
JAmiga:classpath/lib/classpath/jammsg.library: jammsg.library 1.1
JAmiga:classpath/lib/classpath/javaio.library: javaio.library 2.1
JAmiga:classpath/lib/classpath/javalang.library: javalang.library 2.0
JAmiga:classpath/lib/classpath/javanet.library: javanet.library 2.2
JAmiga:classpath/lib/classpath/javanio.library: javanio.library 2.6
JAmiga:classpath/lib/classpath/javautil.library: javautil.library 0.12
JAmiga:classpath/lib/classpath/openjdk.library: gnuclasspath.library 0.1

[JAmiga ENV variables]
CLASSPATH CURRDIR:,$cptemp

[Testing JVM]
JAmiga has been successfully installed!

@TSK
Quote:
Aha!
I believe that last $cptemp might destroy things. Try and do this:
<code>setenv SAVE CLASSPATH CURRDIR:,</code>

The $cptemp thing must have been added by my autoinstall, when an existing classpath env was empty... Or something like that. I'll try to fix that, so no-one else gets the same. But try the setenv, and I hope it'll fix things.

@TSK
So I tried with setting my CLASSPATH to "CURRDIR:,$cptemp", and it works. So that's not your problem.

You however seem to have a few old libraries:

JAmiga:classpath/lib/classpath/javaio.library: javaio.library 2.1
should be 2.2 2013-07-03
JAmiga:classpath/lib/classpath/javalang.library: javalang.library 2.0
should be 2.1 2013-06-11
JAmiga:classpath/lib/classpath/javanio.library: javanio.library 2.6
should be 2.7 2013-08-22
JAmiga:classpath/lib/classpath/javautil.library: javautil.library 0.12

Have you updated all libraries for JAmiga? (I apparently didn't check for those dependencies for the developer kit.)

If you can't find them in AmiUpdate, I have done something terribly wrong somewhere.

i tried jamiga extremely briefly when i installed it, but i was greeted by a crash. this was my first install of jamiga, and it was the latest version (two weeks ago).

i'll check it out again and try to give you a bugreport.

Only console based apps are possible to run yet i believe?
I found this site http://java-apps.org that has a collection of java apps, some of them looks quite nice!

it was hard to find console based apps though.

@spotUP

Yes, only console based stuff currently. I've tried finding existing console applications, but I think we're better of build our own. I had my infamous Twitter example, which merely shows an example of using third party, unmodified JAR files. Its not terribly exiting, but with some clever Arexx-ing I think the use of third-party libraries might be useful. One could theoretically use some sort of Java Google calendar library and synn stuff with limpidclock, for instance. But that requires some amount of Java programming knowledge - but it isn't that hard.

I'm currently looking at enabling a GIT versioning client, but that requires another native library which I haven't finished yet (as described on the blog).

The crash would be interesting seeing!

@jaokim

I removed that $cptemp from the env already and that didn't change anything. Also I downloaded Jamiga from os4depot.net and installed it again just to make sure it was the latest version (before my previous post here). I didn't find any archives from your website. AmiUpdate doesn't have any updates. I will be away from home tomorrow.

@TSK:

That's really strange. I just did the same on my debug system -- installed 1.2 from os4depot, and I found 5 JAmiga updates available in AmiUpdate. I've put a screengrab of it at os4depot. (It hasn't been approved at time of writing this though.)

Do you have more than one installations of JAmiga? Does the assign point to the correct drawer? Is it a fresh reboot? (I'm thinking if the libraries are somehow cached.)

@Joakim

still does not work

I got this from the report



Boot Library Path: JAmiga:classpath/lib/classpath
Boot Class Path: JAmiga:jvm/share/jamvm/classes,JAmiga:classpath/share/classpath

[JAmiga native libraries version]
JAmiga:classpath/lib/classpath/gnuclasspath.library: gnuclasspath.library 0.1
JAmiga:classpath/lib/classpath/jamint.library: jamint.library 1.0
JAmiga:classpath/lib/classpath/jammsg.library: jammsg.library 1.1
JAmiga:classpath/lib/classpath/javanet.library: javanet.library 2.2
JAmiga:classpath/lib/classpath/javautil.library: javautil.library 0.12
JAmiga:classpath/lib/classpath/openjdk.library: gnuclasspath.library 0.1
JAmiga:classpath/lib/classpath/javaio.library: javaio.library 2.2
JAmiga:classpath/lib/classpath/javalang.library: javalang.library 2.1
JAmiga:classpath/lib/classpath/javanio.library: javanio.library 2.7

[JAmiga ENV variables]
CLASSPATH CURRDIR:jAmiga:,

[Testing JVM]
Exception occurred while VM initialising.
java/lang/NoClassDefFoundError: jamvm/java/lang/VMClassLoaderData


I got that last line too when trying to compile the helloworld example

@jaokim

Sorry. My mistake. I did install JAmiga to A1-SE where I didn't have any previous installation. AmiUpdate offered the updates and after updating everything worked fine. Then checking AmiUpdate log on the X why it doesn't find the updates and noticed I had abandoned JAmiga updates. I think there was something like the same update was offered over and over again in the past so I had to disable them or otherwise I don't know why I had disabled them. After updating JAmiga HelloWorld example works fine. I should know this stuff already and still I'm making these kind of mistakes. I'm feeling old because the old dog doesn't learn tricks. Doh ! Sorry !

@JosDuchIt
Quote:

The CLASSPATH is strange; there a comma missing between the assigns, and the JAmiga assign should't need to be there.

Please do this:
<code>
delete ENV:CLASSPATH
delete ENVARC:CLASSPATH

setenv SAVE CLASSPATH CURRDIR:,
</code>

The JAmiga:JAmiga should then hopefully say "JAmiga has been successfully installed!" in the end

You can see current snapshot of what JAmiga:JAmiga should say here: https://code.google.com/p/jamiga2/wiki/CurrentVersion (your's do however look mostly correct.)

<i>If it still doesn't work</i>, could you please verify that you have a file named <b>VMClassLoaderData.class</b> in JAmiga:jvm/share/jamvm/classes/<b>jamvm/java/lang/</b>.

That's basically what this says you don't have:
Quote:

@TSK:

Ah. I was worried I'd be in for a complicated bug hunt... :) Good that it works!

I'm still figuring out the best way to use AmiUpdate for all these tiny updates here and there, hope I've got it sorted now. Soonish I'll be releasing my tiny Twitter application along with some more developer documentation.