| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Built this way it camn only export results via DBUS - or a shared-memory
interface not yet implemented. The DBUS option and enabling define are renamed
so we have a consistent suffix of export/EXPORT.
No logic changes, just some #ifdefs and rearrangements. All regression tests
pass. Code splints clean.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The gpsfix is used before being initialized.
Thanks to Antti Kaijanmaki
|
| |
|
|
|
|
|
|
| |
...but still report eph by re-mixing them in the JSON dumper. This was
worth doing because all regression tests still pass, showing that
visible behavior for old-protocol users gas not changed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I have modified one comment slightly. His explanation follows:
The old code sends one signal, "fix", to DBUS. After
applying the patch, two signals are send. The old signal (to not break
existing applikations) as well as a new signal named "namedfix". (A
DBUS "signal" is kind of a broadcast message containing additional
data, in our case the GPS lon/lat infos, plus some other stuff.) This
"namedfix" contains everything the former "fix" message contained,
plus the GPS device name from where this information originates from.
The problem it fixes is that a DBUS client has no chance to correlate
the data it receives to the installed GPS receivers IFF there is more
than one receiver. They /will/ send different fixes, eg. if they're
several meters apart from each other.
So right now, if you have two GPS receivers with some 10m distance in
between, a DBUS receiver will just see that "one" receiver jumps
between the two positions. With the patch applied, a DBUS client can
distinguish the two (or more) receivers and will be able to correctly
identify the two /different/ locations they are at.
|
|
|
|
|
|
| |
...for those who want to build their own apps linked against libgps and
want the headers to work. Works on OpenBSD, tested by Jeff Francis on
OS X and Linux
|
|
|
|
| |
First line where possible, second line for scripts called with #!
|
| |
|
| |
|
| |
|
| |
|
|
|