Hi Brian,

thanks for the patch.

I agree that you can't use the current source in eclipse without manual work.
When I started with mkgmap and splitter I also started using eclipse (and coding in Java), so
I did more or less the same you did, but I did not dare to say that my
solution is "correct", probably it is far away from being a good solution.

I am not sure if my environment will continue to work with your patch.

1) My current environment looks like this:
- I am using Eclipse "Version: Juno Service Release 2 Build id: 20130225-0426" on a Windows 7 64 bit machine
- I have one directory called d:\eclipse_workspace containing sub directories mkgmap, splitter, display and others
for each project
- the source directories are located in d:\mkgmap or d:\splitter

2) When I try to reproduce problems in older mkgmap releases I close Eclipse, rename e.g. d:\mkgmp to d:\mkgmap_trunk
and do a svn checkout of the wanted sources to d:\mkgmap. Next I use ant dist to build.
After that I start Eclipse and do a refresh for the whole mkgmap project, maybe also a clean.
Sometimes I have to repeat the ant dist and refresh to be able to debug mkgmap in Eclipse.

Depending on the release of mkgmap that I am compiling I have to modify the names of libraries.

If I got it right, you suggest to use the source directory (e.g. d:\mkgmap in my case) also as working directory for Eclipse?

Gerd