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 From: [email protected] Date: Wed, 22 Oct 2014 23:30:18 -0400 To: [email protected] Subject: [mkgmap-dev] Eclipse Hello, I’ve recently downloaded the mkgmap source. I had no trouble compiling it with ant, but getting Eclipse to work took some effort. I’ve attached a patch file containing changes for Eclipse. The specific changes are:* update classpath to find current version of jars* add ivyde settings* add Eclipse setting file to specify source=1.7* add splitter to ivy to compile ‘optional’ bit* update URL of opengeo ivy repository* add bin/tmp to ignore list I see there is a git copy of this project, but it appears all commits are going through svn. I’d prefer to create a pull request on github than to attach a patch file, but am happy to do whatever works. Attached is the patch file for review and merging to http://svn.mkgmap.org.uk/mkgmap/trunk. Regards,Brian _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
