stripped down version

Submitted by dinosoep on Tue, 04/13/2010 - 08:48.

I am curently in the need of a stripped down version, a framework fa a java os.
Just the jvm getting started and running main.java without anything else.
So developpers can experiment with writing a new os from 'scratch'.

‹ how to get started for developing for JNode? i want to code for jnode in java some essentials applications ›

any progress over here? I

Submitted by dinosoep on Sat, 04/24/2010 - 20:19.

any progress over here?
I tried it with the build files but resulted in a bunch of errors XD
is somebody can help?

what errors ?

Submitted by Fabien D on Tue, 04/27/2010 - 18:28.

Fabien

my blog : en français, in english or both

Exactly what I'm looking for (+1)

Submitted by Farok on Tue, 04/13/2010 - 18:33.

Yeah, your right, that's exactly what I'm looking for. As I checked out the JNode source the first time I was kind of disappointed that I could not manage to get only the bloody minimum of the os to do my experiments. I would really like to see that done.

Edit: Ok, I'll look at hagar's solution soon. Would be nice if one could post a tutorial on how to get a system that is able to run the main method, it could save me and others a lot of work, reading through all the build files.

rgds Farok

As explained at

Submitted by hagar on Tue, 04/13/2010 - 14:29.

As explained at http://www.jnode.org/node/798 you can start JNode without all the plugins, by choosing either "JNode (default)" or "JNode (minimal shell)". You can see in the build script which parts are needed, if you want to concentrate on the codebase.

stripped down version (+)

Submitted by gchii on Tue, 04/13/2010 - 14:11.

I agree. Me too.

Quick Howto

Submitted by Peter on Thu, 04/15/2010 - 21:47.

This is a very quick Howto.

Download sources, unpack them and have a look at the files in all/conf/.
Those make a "Jnode distribution".
Mark them _disabled.xml and they will not be built.
Have a look at shell-plugin-list.xml for a quite small configuration, modify it to your needs. It is a list of plugins that will be included in the "initial jar" and be aware of dependencies between plugins, they have to be met (The build system checks for that but the error output might be a bit cryptic, be warned Eye-wink).

And generally be aware: There are simple dependency problems, you want to use classes in java.io you need virtual filesystem. You want System.out,.. you need a textscreen and so on. And when it comes to the classlib it is not yet split largly into single plugins.

The "Main-Class" you're searching for is in the manifest, you'll recognize it...