Da ich ohnehin so wenig blogge und es mir zu aufwendig ist, zwei Blogs zu warten, habe ich mich mit zwei Freunden zusammengetan und ziehe (auch ältere) technische Beiträge nach und nach auf die neue Seite um.

Diesen Blog werde ich daher früher oder später abschalten.

Also ab nach skweez.net und gleich mal einen Kommentar hinterlassen!

Because I blog that seldomly I decided to move to skweez.net, which I operate together with two friends. So go there now and leave a comment!

If svnsync gives something like

Failed to get lock on destination repos, currently held by ...

you have to remove the lock on the destination repository.

svn propdel svn:sync-lock --revprop -r 0 file:///path/to/repo

… does this.

In Eclipse you can enable the SVN commit dialog to show a field for an issue number. You just have to set some SVN properties.

bugtraq:message

This property activates the bug tracking system in Input field mode. If this property is set, then TortoiseSVN will prompt you to enter an issue number when you commit your changes. It’s used to add a line at the end of the log message. It must contain %BUGID%, which is replaced with the issue number on commit. This ensures that your commit log contains a reference to the issue number which is always in a consistent format and can be parsed by your bug tracking tool to associate the issue number with a particular commit. As an example you might use Issue :
%BUGID%, but this depends on your Tool.

bugtraq:number

If set to true only numbers are allowed in the issue-number text field. An exception is the comma, so you can comma separate several numbers. Valid values are true/false. If not defined, true is assumed.

bugtraq:append

true/false. Append or prepend.

bugtraq:url

A URL to the bug in the bugtracking system, e.g. an installation of Bugzilla or Trac, plus the %BUGID%.

If your Eclipse processes don’t terminate on Linux with Gnome, you should disable the Gnome Accessibility. You’re probably hitting this bug: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/293849

Just a small presentation, I held at university about AspectJ.
http://home.in.tum.de/~kanis/aspectj/ (German)

This is the second issue of a series of posts for PS2 development on my blog. Be sure to read the previous articles: part1.

Part 2: Getting SDL

To build SDL, at first you need to install another library named gsKit. This lib is a much lower level graphics library written specifically for the PS2. For an introduction to the hardware architecture of the PS2 please see the excelent article An introduction to PS2DEV by Lukasz Bruun.

Again gsKit is pretty easy to get running. Just download, build and install it:

svn co svn://svn.ps2dev.org/ps2/trunk/gsKit
cd gsKit
make
sudo -E make install

Now you can get SDL and install it. However, when I tried, the current SDL version on ps2dev.org was not compatible with the current gsKit and didn’t compile. To make it compile, load sdl-compile.patch and apply it:

svn co svn://svn.ps2dev.org/ps2/trunk/ps2sdk-ports/sdl
cd sdl
patch -p0 < sdl-compile.patch
make
sudo -E make install

You should be familiar with building the libraries from ps2dev.org now, it’s always the same. If not so, the README will most likely explain the steps to get it running, even if very often they are pretty outdated. Now I leave it up to you to compile the additional SDL libs like SDL_ttf and so on.

In the next post I’ll explain how to write the first SDL program and run it on the PS2.

I just started messing around with development on my PS2. Compiled PS2DEV, PS2SDK and a few libraries like SDL and SDL_ttf for it. As it I found it a bit hard to find enough information to start, I thought I’d write my experiences down.

Part 1: Setting things up

Remember that running your own applications will only work, if your PS2 is “homebrew-capable”. This can be achieved with a mod chip, some disc swapping tool or by using an exploit. Google and Wikipedia know how to that.

PS2DEV is the crosscompiler toolchain for the PS2. You’ll need that for compiling C/C++ code for your PS2.

PS2SDK is a collection of libraries that make accessing the hardware of the PS2 a bit easier. The toolchain alone won’t let you do much without messing around with very lowlevel programming. SDL and other higher level libraries will need this.

Building the toolchain

With the following exports you decide, where the tools are installed. You should probably do this in your .profile or .bashrc or whatever you use to setup your environment.

export PS2DEV=/usr/local/ps2dev
export PS2SDK=$PS2DEV/ps2sdk
export PATH=$PATH:$PS2DEV/bin:$PS2DEV/ee/bin:$PS2DEV/iop/bin:$PS2DEV/dvp/bin:$PS2SDK/bin

Then you can check out the current source:

svn co svn://svn.ps2dev.org/ps2/trunk/ps2toolchain

Now you can build the toolchain and install it:

cd ps2toolchain
make
sudo -E make install

That’s it, it’s simple as that. Of course make will take some time, depending on your machine. This will also install a few additional tools, like ps2client, which I’ll explain later.

Building the SDK

It’s as easy as building the toolchain! Remember that you will have to have your environment variables correctly set.

svn co svn://svn.ps2dev.org/ps2/trunk/ps2sdk
cd ps2sdk
make
sudo -E make install

Now you’ve got the very basic toolset to develop for your PS2. However most beginners (like me) most likely want to develop on something more “sophisticated”. Fortunately SDL is available for the PS2. Read how to compile and install it in part 2.

Important news first: The application goes now by the name Geoclipse.

Since the last update I implemented a GPS plug-in that shows your current position in the map through an attached GPS receiver. Also I am preparing a release on Sourceforge now.

The icons used are from http://www.famfamfam.com/lab/icons/silk/.

That's how it currently looks

Stay tuned!

I made a basic Eclipse application and product out of my SWT port of the mapviewer. It can run standalone without any external dependency to the Eclipse IDE.

Since the last post I ported the last important part that was still left: the rendering code for waypoints.

I also fixed some bugs, did a bigger refactoring and cleaned up some design issues. The tile loading logic should be a bit better now. I’m near a release now, but I want to implement one feature before. That’ll be showing your position in the map through a GPS unit.

If you’re really keen enough, you can check it out from Subversion at https://ssl.byteholder.de/svn/gps https://geoclipse.svn.sourceforge.net/svnroot/geoclipse.

My Mapviewer port is now running stable enough, that I created an Eclipse Plug-In using it.

Most things, like pan and zoom, work. The threading issues are also ironed out. It’s not ready for a release yet, though. Still missing is support for overlays.

A picture says a thousand words: