
Typographical conventions © 2007, QNX Software Systems GmbH & Co. KG.
In ksh and bash shells, All shell scripts are executed in a sub-shell by default.
Therefore, it’s important that you use the syntax
. <script>
which will prevent a sub-shell from being used.
Each DDK is rooted in whatever directory you copy it to. If you type
make within
this directory, you’ll generate all of the buildable entities within that DDK no
matter where you move the directory.
all binaries are placed in a scratch area within the DDK directory that mimics the
layout of a target system.
When you build a DDK, everything it needs, aside from standard system headers, is
pulled in from within its own directory. Nothing that’s built is installed outside of
the DDK’s directory. The makefiles shipped with the DDKs copy the contents of
the
prebuilt directory into the install directory. The binaries are built from
the source using include files and link libraries in the
install directory.
Typographical conventions
Throughout this manual, we use certain typographical conventions to distinguish
technical terms. In general, the conventions we use conform to those found in IEEE
POSIX publications. The following table summarizes our conventions:
Reference Example
Code examples if( stream == NULL )
Command options -lR
Commands make
Environment variables PATH
File and pathnames
/dev/null
Function names exit()
Keyboard chords
Ctrl-Alt-Delete
Keyboard input something you type
Keyboard keys Enter
Program output login:
Programming constants NULL
Programming data types unsigned short
Programming literals 0xFF, "message string"
Variable names stdin
continued. . .
xii About the USB DDK September 10, 2007
Komentáře k této Příručce