checkout & compile

If you want to compile our code yourself, you first need to have an account at our cvs. Get in contact with bach to get one. If you are not familiar with Java, or Eclipse, you probably don't want to compile the plugins anyway, but merely use the released toolkits - see installation.

If you know you want to check out and compile, because you want to support our work on the core components or the toolkit, I shall assume you know your way around Eclipse already.

To check out and compile the core, follow the instructions below:

1. Get an Eclipse 3.0 installation. Older versions than Eclipse 3.0RC2 will not work!
2. Start it and open the CVS Synchronization perspective.
3. Add the micropsi repository. (See CVS for details.)
4. Open the repository, go to HEAD
5. Select org.micropsi.core, right-click and select "Check out as..."
6. Check it out as a project in the workspace, the proposed name is fine
7. Go to the Java perspective. If you are on Windows, the project should show no errors: It's already compiled and ready-to use. (To rebuild components, use the ant script in the "build" directory.) If you are not on Windows, you will need to adjust one dependency: swt.jar. Do this by

1. going to the project's properties
2. selecting "Java Build Path"
3. selecting the entry with the "!", should be the third one
4. clicking "Edit"
5. clicking "Extension"
6. and selecting the appropriate swt.jar for your operating system. It's /plugins/org.eclipse.swt.gtk_3.0.0/ws/gtk/swt.jar for Linux/GTK, for example.

You're done if you only wanted the core. If you also want the plugins, here we go:

1. Go to the CVS Repositoy perspective
2. Open the repository, select the HEAD
3. "Check out as...": org.micropsi.runtime (just click "Finish")
4. Go to the Java perspective and check if everything is compiled and fine after checkout is complete.

Repeat these steps with the following modules (in exactly this order):

1. org.micropsi.console
2. org.micropsi.agentmanager
3. org.micropsi.mindconsole
4. org.micropsi.worldconsole

All of these should compile without further modifications after checkout. You now have a complete toolkit.

When you first start a runtime workbench with the plugins enabled and access a Micropsi view, the MRS will try to start up and ask you for some components. (The MRS is able to load components on-demand so they don't need to be in the runtime workbench's classpath when it starts up.)

The required "core" components can be found in the "dist/lib" directory of the core project, neatly packaged into jars. (If you created them with the ant script in the "build" dir, that is.)

So, when the MRS asks you about its components, select these jars from your filesystem. (Use the "Browse" button to find your WORKSPACE/org.eclipse.core/dist/lib directory.) You only need to do this at the first MRS startup, the runtime plugin will remember where you keep your components. You can change the component paths at the MRS' preference page.

Remember: Everytime you change something that is part of, or loaded by, the MRS, you need to rebuild your components with ant. The runtime workbench always works with the component jars you specify, not the current binaries from the core project!

There are two exceptions, though: the net and commons libraries. If you change these, you will not only have to rebuild with ant, you also need to copy the newly created libs to the org.micropsi.runtime/libs directory. (Net and Commons are not loaded dynamically, as there are compile-time dependencies on these two libs. You probably don't want to hack the nets or the basic stuff in the commons jar anyway. Do you?)