Accessing GPSD on remote linux host, client running on Windows #11
Comments
|
Viking uses libgps to communicate with GPSD. AFAIK there is no Windows version of libgps ATM. Quote from GPDs website "No, we don't support Windows — get a better operating system." However I think this is more for gpsd (the server) more than the libgps (the client - as used with Viking). With the new cross compile tool chain working for Viking (and for other programs too), it will be quite possible for me to try building libgps for Windows and see if it is a) possible and then b) usable. AFAIK There has been some previous investigation into this (http://lists.nongnu.org/archive/html/gpsd-dev/2012-08/msg00008.html) but no confirmed outcome as of yet. |
|
Accessing some Linux system running GPSD from Windows via libgps would be very welcome. Else, on Windows (or cross-platform applications) developers must follow the "bad idea to speak the protocol directly" (gpsd_json(5)). Any news? |
|
GPSD now has support to build a Windows version of libgps. Hopefully there will soon be an official release of GPSD 3.17 which will have this in. I have code ready in Viking to take advantage of this, but then there's the question of when an updated Viking release will be made too. |
|
Thanks for the update. GPSD site only provides up to 3.16, so we (Stellarium) will update then. |
|
Viking 1.7 now includes a GPSD 3.17 client on the Windows installation. Derived from https://build.opensuse.org/package/show/windows:mingw:win64/mingw64-libgps I don't know if GPSD v3.17 client works with a GPSD server v3.18 (possibly not - so you may have to run the same versions at both ends). ATM I don't have the inclination to create a libgps.dll v3.18, nor offer some kind of option in the Windows installer to be able to choose a specific version (or if this is even sensible since v3.18 changed the client API interface - so I think one needs to build Viking itself for the specific API version...). |
By altering the emit_update() functions we can generally find all the places where a change has been made, since any change should be causing the display to update. Some places causing updates such as moving, zooming the display etc... are then marked as not modifying the project. Further for layer properties, we now check each individual property to see if has changed. Otherwise selecting OK when nothing has actually changed would set the modified flag. Particularly if one often views large .vik files, then changing the visibility of items may be considered just part of the viewing process. The setting 'modifications_ignore_visibility_toggle' can then be set, to avoid being notified about visibility changes.
Feature request: Make the Windows version communicate with GPSD via the socket interface(JSON) over a network.
The text was updated successfully, but these errors were encountered: