Building DDKs

The Character DDK package can be downloaded from Foundry27.

The latest source code can also be downloaded at Foundry27:BSPs and Drivers Source code .

You can compile the DDK from the IDE or the command line.

• To compile the DDK from the IDE:

  Please refer to the Managing Source Code chapter, and "QNX Source Package" in the Common Wizards Reference chapter of the IDE User's Guide.

• To compile the DDK from the command line:

  Please refer to the release notes or the installation notes for information on the location of the DDK archives.

  DDKs are simple zipped archives, with no special requirements. You must manually expand their directory structure from the archive. You can install them into whichever directory you choose, assuming you have write permissions for the chosen directory.

  The following example indicates how you create a directory and unzip the archive file:

  # cd ~
  # mkdir ddk_install_dir
  # cd ddk_install_dir
  # unzip /path_to_ddks/ddk-device_type.zip
  # make
  

  Then you should get binaries and libraries in ddk_install_dir/install .

  The top-level directory structure for the DDK looks like this:

  Figure 1. Directory structure for this DDK.
  Note: Historically, you had to run:

  . ./setenv.sh
  

  to set up the environment variable of the installation directory's make. This method is no longer required, as all the directories in /src have been set up to install their binaries and libraries to ddk_install_dir/install.

  Additionally, on Windows hosts you'll need to run the Bash shell (bash.exe) before you run the make command.

  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 /install 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.