Belkin F8E211 Betriebsanweisung Seite 12

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 114
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 11
Building DDKs 2006, QNX Software Systems GmbH & Co. KG.
You must run:
. ./setenv.sh
before running make,ormake install.
Additionally, on Windows hosts you’ll need to run the
Bash shell
(
bash.exe) before you run the . ./setenv.sh command.
If you fail to run the
. ./setenv.sh shell script prior to building
the DDK, you can overwrite existing binaries or libs that are installed
in
$QNX TARGET.
Each time you start a new shell, run the
. ./setenv.sh command.
The shell needs to be initialized before you can compile the archive.
The script will be located in the same directory where you
unzipped the archive file. It must be run in such a way that it
modifies the current shell’s environment, not a sub-shell
environment.
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.
xii About the USB DDK November 2, 2006
Seitenansicht 11
1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 113 114

Kommentare zu diesen Handbüchern

Keine Kommentare