View Single Post
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#20
I have just published a new release: 0.3.0.

0.3.0 release is built against libosmscout release https://github.com/rinigus/libosmsco...0.git.20161110 . I am going to tag libosmscout versions, so you could always build corresponding Import tool.

For end users, the main change is in fixing multiple bugs related to routing in the libosmscout library by its authors: segfault at certain conditions reported by @otsaloma (thank you!), taking the wrong turns, and few others.

There are several important changes "under the hood". I am using now GNU Libmicrohttpd to provide HTTP backend. As a result, the clients can use up to 100 connections served using as many threads as there are CPUs on your device. The limit of connections is hard-coded, but if there is a huge interest in specifying it as an option, I will add it. This change should simplify the client's side of communication since it would not have to worry about exceeding the limit.

The server is now built using static linking to libosmscout, marisa, and libmicrohttpd. Its mainly done for two reasons: libosmscout API is changing as it is developed leading to incompatibilities between the versions; there is no need for other RPMs as you install the server. After an upgrade, I suggest to remove libosmscout-qt and libmarisa from your devices. I am planning to drop these packages from OpenRepos a bit later when users would move to 0.3.0 or later release.

NB! When you start using a new version, please update the maps! Few bugs were fixed in libosmscout library by fixing an importer. So, to get these fixes, you would have to update the maps with the latest version.

I have added a session log (see Settings to enable it). You could use it when reporting bugs to get the corresponding URL.

If your favorite client does not support routing yet, but supports GPX, you could now calculate the route and save the result in GPX format (see URL parameters in server GitHub project page).
 

The Following 10 Users Say Thank You to rinigus For This Useful Post: