Posts Tagged ‘QNX’

Building Boost.Python 1.42 for QNX 6.4.1

June 8, 2010

Building the Boost C++ libraries ( for QNX is pretty straight forward. The build can be executed as described in the Boost documentation. I have performed the build of Boost 1.42 using QNX 6.4.1 installed in a virtual machine.

But there was a little tweak required to build the Boost.Python library. The problem is that python is located in /usr/qnx641/host/qnx6/x86/usr/bin/python but the required Python include files like Python.h are located in /usr/qnx641/target/qnx6/usr/include/python2.5. This setup is confusing the automatic detection of the include files used in the build process.

This can be fixed by providing the right include path, e.g by adding the following line to the file <boost_src_dir>/project-config.jam:

using python : 2.5 : /usr/qnx641/host/qnx6/x86/usr/bin/python : /usr/qnx641/target/qnx6/usr/include/python2.5 ;

Often used pkgsrc commands

August 14, 2008

This my memo where I store the commands I’m using when building packages with pkgsrc (

Determining the package dependencies:
$ bmake show-depends-pkgpath

Finding build references to a given package, e.g. libdrm:
$ egrep ‘libdrm|xf86driproto’ */*/

All the available targets are documented in The pkgsrc make target reference – NetBSD Wiki.

This is used to rebuild a patched package:
bmake distinfo && bmake clean && bmake build

The following builds and install the package:
bmake distinfo && bmake clean && bmake package

QNX specific issues are discussed in the forum

Building libcURL for QNX 6.3.2 and Windows XP from source

August 14, 2008

To have access on files using FTP, HTTP and directly from file system I use the free library libcurl. Another important aspect is portability as the application should work on QNX using qcc/gcc 4.2.3 and on Windows using VC9/VS2008. So I give libcurl a try. The build process for libcURL is as stated in the documentation very straight forward. But there where two little pitfalls discovered when using VS2008.


Script fails with “No such file or directory”

July 9, 2008

While running a script it fails immediately with “No such file or directory“. Even a print or echo command in the second line of the script is ignored. The used program to process the script does exist and is running, too. In this case checking the line endings may help:

file nameofthescript

will report:

ISO-8859 English text, with CRLF line terminators

but expected is:

ISO-8859 English text

The problem are the CR/LF line endings. These are typically used from MS Windows applications. Correct the line endings using any editor. For MS Windows try the Notepad++ open source editor. It has a build-in menu item to fix the line endings: Format -> Convert to Unix.