1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
Here are the steps for installing gpsd and verifying its performance:
0. The only prerequisites you will absolutely need to build the suite
are C and C++ compilers: C for the gpsd daemon itself and its client C
library, C++ for the C++ client-library wrapper. You will also
need autotools; automake 1.10 or later and autoconf 2.61 or later
The code depends on one non-C99 feature: anonymous unions. We could
eliminate these, but the cost would be source-level interface breakage
if we have to move structure members in and out of unions.
Having the following optional components on your system will enable
various additional capabilities and extensions:
pthreads library -> support for PPS timekeeping on serial GPSes
DBUS -> gpsd will issue DBUS notifications
X windows + lesstif -> two test clients depend on this
ncurses -> two more test clients depend on this
Python -> most of the test and profiling tools are in Python
For building from SVN, or if you change the man page source, xslt and
docbook xsl style files are used to generate nroff -man source from
docbook xml. The following packages are used in this process:
libxslt -> xsltproc is used to build man pages from xml
docbook-xsl -> style file for xml to man translation
The build degrades gracefully in the absence of any of these. You should
be able to tell from configure messages which extensions you will get.
1. Start by making sure you can get data from your GPS, otherwise the later
steps will be very frustrating. In this command
stty -F /dev/ttyXXX ispeed 4800 && cat </dev/ttyXXX
replace ttyXXX with the filename of the port. This will probably be
either /dev/ttyUSB0 or /dev/ttyS0. When you run this command, you
should see text lines beginning with $ come to stdout (possibly after
a short initial burst of binary garbage). If you don't see this, you
may have OS-level problems with your serial support, but more likely
have the wrong device. Look again.
2. Ensure that device permissions will enable gpsd to read from and
write to GPS devices even after it drops root privileges. If you are
running Fedora Core or Ubuntu you can skip this step, as the stock
configuration has the right properties.
gpsd requires two things: (1) that GPS devices have group read and
write enabled, and (2) all of them are have the same group ID as a
prototypical device, typically /dev/ttyS0 under Linux or /dev/tty00
under *BSD. It does not actually matter what the owning group is,
as gpsd will look this up on startup. Alternatively, (3), you can
set a fallback group with the enable-gpsd-group in case the prototype
is not found: this should be the "dialout" group (or functional equivalent)
that has write access to serial devices.
Before dropping privileges, gpsd will ensure that it has access to
devices given to it on the command line by forcing their group read
and write permissions on.
On a Linux with udev, check the files in /etc/udev/permissions.d to
ensure that /dev/tty* devices are all created with the same group
and with 0660 permissions.
When gpsd drops privileges, its default is to set uid to 'nobody' and
group to the owning group of the prototype device (the configure
option --enable-gpsd-user=foo will cause gpsd to change to 'foo'
instead).
If your system has the Linux hotplug facility installed you can skip
the permission-setting part; the hotplug scripts will force the
permissions for you. You still have to make sure all the tty devices
are in the same group.
3. Build gpsd from source (skip this step if you have installed a gpsd
binary package).
You will need to have either Motif or LessTif installed in order for
xgps and xgpsspeed to build; if you don't, you'll get some error
resembling "Xm/Xm.h: No such file or directory". If you're on a Linux
system, you may already have LessTif. Source code is available
from <http://www.lesstif.org/>.
Under Ubuntu, you will require libmotif-dev, libxp-dev and libxaw7-dev
in addition to the standard build-support packages. You can get
all the build prerequisites intalled with "apt-get build-dep gpsd".
To build from source, run ./autogen.sh (or sh autogen.sh if the
script does not have execute permission). Mac OS X users may
need to do "./autogen.sh --x-includes=/usr/X11R6/include"
Note: if you are going to use the RTCM-104 support, you should compile
with gcc4; if you don't have it installed as your default
compiler, do this by specifying CC=gcc4 before the autogen.sh
command. The rtcm2.c file confuses the gcc-3.4.[23] optimizer
at -O2 level, making it generate incorrect code.
Then run make: libgps.so, gpsd, xgps, and xgpsspeed will be
built. Copy the app-defaults files xgps.ad and xgpsspeed.ad to your
home directory or to the system-wide X app-defaults directory.
4. Start gpsd. You'll need to give it as an argument a path to
a serial or USB port with a GPS attached to it.
5. Once gpsd is running, telnet to port 2947. You should see a
greeting line that's a JSON object describing GPSD's version.
Now plug in your GPS (or AIS receiver, or RTCM2 receiver).
6. Type '?WATCH={"raw:1"};' to start raw and watcher modes. You
should see NMEA data (text lines beginning with $) spewing out. You
will also see lines beginning with '{' that are JSON objects
representing reports from your GPS; these are packet translations in
GPSD protocol.
7. Start the xgps client. Calling it with no arguments should do the right
thing. You should see a GUI panel with position/velocity-time information,
and a satellite display. The displays won't look very interesting until
the GPS acquires satellite lock.
8. Now that you've verified that the code is working, "make install"
will install it it in the system directories. "make uninstall" will
undo this.
(You won't need to "make install" if you installed from a binary package.)
9. To enable hotplugging of USB GPSes under Linux, do a 'make udev-install' or
equivalent to put the appropriate udev rules and wrapper files in plases.
10. Check out the list of supported hardware at
http://gpsd.berlios.de/hardware.html
If your GPS isn't on the list, please send us information to add a new
line to the table. Directions are included on that page.
We can also use updates of the latest version number known to work with
hardware already supported.
11. Note for small embedded systems and those without threading. It is
possible to build gpsd without thread support if you configure with
--disable-pps. You'll lose support for updating the clock from PPS pulses.
It's also possible to build without Python via --disable-python, in which
case you'd build won't make Python libraries and "make install" won't
try to install Python tools.
12. Note for systems using DBUS: gpsd includes support for shipping fixes
as DBUS notifications, but it is not compiled in by default. Configure
with the option "--enable-dbus" to get it working.
13. The distribution includes a PHP script that you can use to
generate a PHP status page for your GPS. You will need php and php-gd
installed. To install it, copy the file 'gpsd.php' to your HTTP
document directory. The first time it's invoked, it will generate a
file called 'gpsd_config.inc' containing configuration information;
edit to taste. Note that for the Google Maps feature work you need
to set a valid Google API key in your config file.
14. There are regression tests to verify proper operation of gpsd, and
it can be useful to run these to verify that all is well. To run the
regression tests, first build gpsd from sources, and then run "make
testregress". It is not necessary to install first. Python is
required for regression tests.
|
