Updated MapsforgeWrapper

This commit is contained in:
ClemensFischer 2026-02-13 13:27:08 +01:00
parent da2d7c4e0a
commit ff4e446c03
3 changed files with 7 additions and 11 deletions

View file

@ -28,11 +28,12 @@ namespace MapsforgeWrapper
else
{
var multiMapDataStore = new MultiMapDataStore(MultiMapDataStore.DataPolicy.DEDUPLICATE);
dataStore = multiMapDataStore;
foreach (var file in Directory.EnumerateFiles(mapFilePath, "*.map"))
{
multiMapDataStore.addMapDataStore(new MapFile(file), false, false);
}
dataStore = multiMapDataStore;
}
}

View file

@ -20,11 +20,6 @@
</repositories>
<dependencies>
<dependency>
<groupId>com.github.mapsforge.mapsforge</groupId>
<artifactId>mapsforge-core</artifactId>
<version>0.27.0</version>
</dependency>
<dependency>
<groupId>com.github.mapsforge.mapsforge</groupId>
<artifactId>mapsforge-map-awt</artifactId>

View file

@ -29,12 +29,12 @@ map.MapLayer = new MapTileLayer
---
Apparently, IKVM's `MavenReference` does not work with other Maven repositories than Maven Central.
Mapsforge however, is hosted by JitPack. So the currently only working way to utilize Mapsforge is
by creating a local JAR file with all dependencies required by `TileRenderer` and reference it via
`IkvmReference`.
Building MapsforgeWrapper with IKVM's `MavenReference` fails - apparently because a dependency
on the XML Pull Parser library could not properly be resolved. So the currently only working way
to use Mapsforge is by creating a local JAR file with all dependencies required by MapsforgeWrapper
and reference it via `IkvmReference`.
This means that you need [Maven](https://maven.apache.org/) to build the MapsforgeWrapper library.
This means that [Maven](https://maven.apache.org/) is needed to build the MapsforgeWrapper library.
There is a custom `PreBuild` event in `MapsforgeWrapper.csproj` which executes the command
```
mvn package