• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - myrkraverk

#1
I have put my preliminaries on the java7os2 project's dev mailing list:

https://java7os2.dev.java.net/servlets/SummarizeList?listName=dev

Next I will start to setup my dev environment and port the build system (as in the TODO post), starting with this:

http://www.smedley.info/os2ports/index.php?page=build-environment

I'll post more stuff to the dev list, as I get there.
#2
Thank you, I didn't know about the java7os2 project.  I am going to move/repost my thoughts/experiments to their dev mailing list, and see what happens.

As for helping out for non-developers: There are always tasks at hand.  For example, with a project like this with external moving sources, there is syncing up with the outside world.  And during the initial stages, when there are multiple build failures, it is making sure once a file/component builds, it stays built -- that is, it is very easy to miss breaking one file, while working on something seemingly irrelevant.

Have fun
#3
Open Bounties / And now, for OpenJDK 7
2009.02.07, 18:14:23
Well, that is assuming pretty much, and is quite untimely ;)

Step zero: settle on a project name (ecsJ? -- jdk/2 is probably too close to the openjdk and java 2 trademarks) and set up a repository os/2 users can access.  Porting mercury isn't something to spend any effort on (if we have it already -- yay!).

The first step is porting the build system.  This mostly involves copying and renaming files, and modifying make files.  No Java/C++ knowledge is truly necessary, though knowing how to use a compiler is a big plus.  Familiarity with (or willingness to learn) unix scripting and makefiles is a must though.  I am assuming it's possible to modify the build system to use precompiled class files instead of a bootstrap jdk.

The next step is to try to build.  And this is the step where unforeseen dependencies will hit, and hit hard.  I know that to be able to build world, CUPS is required, though I hope it's not for Hotspot.  Smedleys CUPS may or may not work; at least my /opt/csw/include/cups/cups.h wasn't sane enough, so I had to tell the build system to use my /usr/include/cups/cups.h.  (I don't know why it found the former first).  There will certainly be some gaps that must be filled in, by direct porting, and maybe some with additions to the Netlabs libc.  It will take some time and effort to get everything to build.  Then there are the issues when we try to link.  I don't think that will be painless.

At this time, we can try to use the jvm, and will probably run into one segfault after another and/or even worse errors due to thread synchronization (those will be hard to debug).  It is time to try and build javac and the related tools, if that wasn't attempted concurrently.

Independent of all this, is to convert man pages to help files (.inf isn't it?).  Some kind soul with little or no technical background can do this -- particularly if she has translation experience.

By now, it's time to think about publishing, and seeing about java conformance testing.  And of course, to tell the world.


Have fun

#4
[Apologies if this is a repost, this forum is teasing me]

I have taken a cursory look at OpenJDK 1.7 (or is that just plain 7?) and have managed to compile it on solaris.

Hotspot, the jvm, is divided into common, cpu specific, os specific and cpu+os specific sources, and these will have to be translated.  An added complication is that it requires at least JDK 1.6 to build.  I don't know enough about the build system (yet) to tell if it's possible to bring over pre-compiled class files.

Porting awt is then completely different story, and quite unlikely to be successful (by me) unless there is some sort of xlib between awt and pm.  However, someone familiar with pm programming may be able to make use of the windows code.

The unix api project on netlabs is probably going to help a lot.  Though I don't know how complete it is.  If it has pthreads, things are already looking pretty good.  Though it's probably better, to have real native code for threads, for added confidence of correctness.
#5
I am also getting no kbd events to the guest os (FreeDOS) and have ended up killing VirtualBox.

I created the disk image and virtual machine with the gui.  If there is anything I can do to help out find why there are no events, just let me know.


Johann