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 ;

$ svn info
svn: Der Client ist zu alt, um mit der Arbeitskopie ».« zusammen zu arbeiten;
bitte besorgen Sie einen neueren Subversion-Client

Get the following  LPIA binaries for the Dell Mini 9  from

lpia build of subversion 1.5.1dfsg1-1ubuntu2~hardy2 in ubuntu hardy BACKPORTS

• libsvn1_1.5.1dfsg1-1ubuntu2~hardy2_lpia.deb
  (680.4 KiB)
• subversion_1.5.1dfsg1-1ubuntu2~hardy2_lpia.deb
  (1.2 MiB)

Install the downloaded files using this command:

$ sudo dpkg -i libsvn1_1.5.1dfsg1-1ubuntu2~hardy2_lpia.deb subversion_1.5.1dfsg1-1ubuntu2~hardy2_lpia.deb

On the right side of the page are links to successfully performed builds for LPIA. This final page (https://launchpad.net/ubuntu/+source/sun-java6/6-14-0ubuntu1.8.04/+build/1103045) contains links to the packages to download:

• sun-java6-bin_6-14-0ubuntu1.8.04_lpia.deb
  (27.7 MiB)
• sun-java6-demo_6-14-0ubuntu1.8.04_lpia.deb
  (11.6 MiB)
• sun-java6-jdk_6-14-0ubuntu1.8.04_lpia.deb
  (17.7 MiB)
• sun-java6-plugin_6-14-0ubuntu1.8.04_lpia.deb
  (1.9 KiB)
• sun-java6-jre_6-14-0ubuntu1.8.04_all.deb
  (6.1 MiB)
  (from page https://launchpad.net/ubuntu/hardy/lpia/sun-java6-jre/6-14-0ubuntu1.8.04)

The last mentioned JRE package can be found on Binary Package “sun-java6-jre” in The Hardy Heron for lpia (lpia). I do not know why the packages are located on different web pages and not on a single one.

Install the files directly using gdebi or after downloading with this command in a single line:

sudo dpkg -i  sun-java6-jre_6-14-0ubuntu1.8.04_all.deb
     sun-java6-bin_6-14-0ubuntu1.8.04_lpia.deb
     sun-java6-plugin_6-14-0ubuntu1.8.04_lpia.deb
     sun-java6-jdk_6-14-0ubuntu1.8.04_lpia.deb

Now even Fullscreen Java Applications should work as expected. I’ve tested the example from http://java.sun.com/docs/books/tutorial/extra/fullscreen/index.html and it really shows a full screen application.

warning LNK4099: PDB 'vc90.pdb' was not found with ...

The problem is that the object files embeds the path to the PDB file. The following steps extracts the object file from the library and shows the embedded path.

C:\>lib /list al.lib
Microsoft (R) Library Manager Version 9.00.30729.01
...
.\Debug\alIP_Winsock.obj
...

C:\>lib /extract:.\Debug\alIP_Winsock.obj al.lib
Microsoft (R) Library Manager Version 9.00.30729.01

C:\>dir *.obj
...
30.06.2009  13:53            48.195 alIP_Winsock.obj
...

C:\>dumpbin /section:.debug$T /rawdata  alIP_Winsock.obj
Microsoft (R) COFF/PE Dumper Version 9.00.30729.01
...
Dump of file alIP_Winsock.obj
...
RAW DATA #3E
00000000: 04 00 00 00 6E 00 15 15 D1 E3 36 F9 6E D3 E4 4E  ....n...Ñã6ùnÓäN
00000010: 92 D2 08 70 C2 43 72 F6 01 00 00 00 63 3A 5C 5F  .Ò.pÂCrö....c:\_
...
00000030: 6F 61 5C 63 6F 64 65 5C 64 70 77 73 63 6F 72 65  oa\code\dpwscore
00000040: 2D 32 2E 31 2E 30 5C 70 6C 61 74 66 6F 72 6D 5C  -2.1.0\platform\
00000050: 76 73 32 30 30 38 5C 77 69 6E 33 32 5C 61 6C 5C  vs2008\win32\al\
00000060: 61 6C 5C 64 65 62 75 67 5C 76 63 39 30 2E 70 64  al\debug\vc90.pd
00000070: 62 00 F2 F1                                      b.òñ
...

Fixing this problem is done by setting the Program Database File for the object file and the library to the same setting.

Here are the location in the VS2008 Project Properties:

Project Configuration Properties -> C/C++ -> Output Files
Program Database File

This name, e.g. $(IntDir)\vc90.pdb, is embedded into the object file and it should be the same as the one in

Project Configuration Properties -> Linker -> Debugging
Generate Program Database File

This is, e.g. $(TargetDir)$(TargetName).pdb

Now the object file contain the path where the library is located, too.

...
RAW DATA #3E
00000000: 04 00 00 00 56 00 15 15 3E 7B 32 F1 12 86 51 48  ....V...>{2ñ..QH
00000010: 97 34 6B AC 14 85 20 C2 01 00 00 00 63 3A 5C 5F  .4k¬.. Â....c:\_
...
00000030: 6F 61 5C 63 6F 64 65 5C 74 6F 6F 6C 73 5C 64 70  oa\code\tools\dp
00000040: 77 73 63 6F 72 65 62 75 69 6C 64 5C 64 65 62 75  wscorebuild\debu
00000050: 67 5C 61 6C 2E 70 64 62 00 F3 F2 F1              g\al.pdb.óòñ
...

Here are the Properties as used within a VS C++ Project file (.vcproj) or Property file (.vsprops):

<Tool
Name=”VCCLCompilerTool”
ProgramDataBaseFileName=”$(TargetDir)$(TargetName).pdb”
/>
<Tool
Name=”VCLinkerTool”
ProgramDatabaseFile=”$(TargetDir)$(TargetName).pdb”
/>

<br />  <Tool<br />    Name="VCCLCompilerTool"<br />    ProgramDataBaseFileName="$(TargetDir)$(TargetName).pdb"<br />  /><br />  <Tool<br />    Name="VCLinkerTool"<br />    ProgramDatabaseFile="$(TargetDir)$(TargetName).pdb"<br />  /><br />

To have a deeper look at this issue it may help to start Python in more verbose mode using the option -v:

python -vv

The printed messages are listing different attempts to load the required module with different names in different locations. Finally dlopen is called with the .so file named module.so. Afterwards the names of the unknown symbols are shown. An unknown symbol is a reference to a function or method that should be available at runtime but the loading mechanism can not find the required resource.

On QNX some more information about the loading process of dlopen are available. To enable these information use

export DL_DEBUG=1

from the shell or from Python

os.environ['DL_DEBUG'] = ’1′

to get a more verbose dlopen.

To have a look at the specific dynamic .so module it is possible to use the linker ld. Use the option -M or –print-map to print a link map. More options are available from the manual of ld, e.g. the one for GNU ld of the binutils package is available from http://sourceware.org/binutils/docs/ld/index.html.

To ensure that that a dynamic module has no undefined symbols the linker option –no-allow-shlib-undefined may be used. Depending on the build process it may be possible to add the following line to the Makefile:

LDFLAGS+=-Wl,–no-allow-shlib-undefined

A convenient way to install PyDev is using this update site from the Eclipse update manager: http://pydev.sourceforge.net/updates/

After selecting the PyDev perspective inside Eclipse the first step would be to set the path to the python executable in Window->Preferences->PyDev. For downloading and installing Python more information is available from http://python.org.

To ensure a better quality of the python programs it is advisable to add pylint from http://www.logilab.org/857. These are the required step for installation:

First install EasyInstall from http://peak.telecommunity.com/DevCenter/EasyInstall by downloading and executing ez_setup.py , e.g. in a cmd.exe window:

> python ez_setup.py
Downloading http://pypi.python.org/packages/2.5/s/setuptools/setuptools-0.6c8-py2.5.egg
Processing setuptools-0.6c8-py2.5.egg
Copying setuptools-0.6c8-py2.5.egg to c:\programme\python\2.5\lib\site-packages
Adding setuptools 0.6c8 to easy-install.pth file
Installing easy_install-script.py script to C:\Programme\python\2.5\Scripts
Installing easy_install.exe script to C:\Programme\python\2.5\Scripts
Installing easy_install-2.5-script.py script to C:\Programme\python\2.5\Scripts
Installing easy_install-2.5.exe script to C:\Programme\python\2.5\Scripts

Installed c:\programme\python\2.5\lib\site-packages\setuptools-0.6c8-py2.5.egg
Processing dependencies for setuptools==0.6c8
Finished processing dependencies for setuptools==0.6c8

Do not miss to add a path to the Scripts subdirectory of python where the easy_install.exe is located.

Then install pylint as it is mentioned on http://www.logilab.org/card/pylint_easyinstall:

> easy_install http://release.ingeniweb.com/third-party-dist/logilab.installer-0.1.tgz
Downloading http://release.ingeniweb.com/third-party-dist/logilab.installer-0.1.tgz
Processing logilab.installer-0.1.tgz
Running logilab.installer\setup.py -q bdist_egg --dist-dir c:\temp\easy_install-mzyl5s\logilab.installer\
egg-dist-tmp-nbegf0
Adding logilab.installer 0.1dev to easy-install.pth file

Installed c:\programme\python\2.5\lib\site-packages\logilab.installer-0.1dev-py2.5.egg
Processing dependencies for logilab.installer==0.1dev
Searching for pylint==0.14
Reading http://pypi.python.org/simple/pylint/
Reading http://www.logilab.org/project/name/pylint
Reading http://www.logilab.org/projects/pylint
Best match: pylint 0.14.0
Downloading ftp://ftp.logilab.fr/pub/pylint/pylint-0.14.0.tar.gz
Processing pylint-0.14.0.tar.gz
Running pylint-0.14.0\setup.py -q bdist_egg --dist-dir c:\temp\easy_install-ztwn3u\pylint-0.14.0\egg-dist
-tmp-vng8y2
.....

The last step is to add pylint.bat to the Pydev preference, e.g. as C:\Programme\python\2.5\Scripts\pylint.bat in my setup. Invoking pylint.bat from within Eclipse leads to a “SyntaxError: invalid syntax” message in the first line. Remove the first line with the @echo off and everything works like a charm.

Thread[0] 1 <symbol is not available>

The corresponding source is displayed as:

No source available for “”

[View Disassembly ...]

The launch of the target is terminated by a time out.

If you are hit by the above scenario, check the following things:

1. Executable for the target is compiled for Debugging, e.g. -g is used for the gcc/qcc. Clean the project when changing the build options.
2. If you are using Momentics IDE Tau, verify that you are using the latest qconn and the latest gdb. As described on http://community.qnx.com/sf/wiki/do/viewPage/projects.ide/wiki/Builds_Tau_Integration you get the latest qconn from http://community.qnx.com/sf/frs/do/downloadFile/projects.ide/frs.ide_integration_builds.momentics_632_patch_for_profiler/frs1426?dl=1.
3. The latest GDB version for QNX is as described on the Wiki http://community.qnx.com/sf/projects/toolchain available from http://community.qnx.com/sf/frs/do/listReleases/projects.toolchain/frs.gdb.

> TFPT.exe /online

fails with the message

Unable to determine the workspace.

If this is the case for a workspace created with Visual Studio 2008 try to change the workspace from Visual Studio 2005. Even only changing the comment was sufficient in my case. After this change everything works again from TPFT and VS 2008, too.

To install it add for IDE 4.5 (Tau) the Eclipse 3.3 update site to Help->Software Updates->Find and install… . Select the radio button named “Search for new features to install” and click Next. Then it is possible to add a “New Remote Site…”.

For most distributions of Eclipse, there should already be a “Europa Discovery Site” defined in the Update Manager. Otherwise you can add the following URL as a remote update site in the update manager.

http://download.eclipse.org/releases/europa/

See Eclipse Help for general information about using Update Manager.

To get the latest version of Mylyn you may add the Mylyn update site, too. This is the necessary URL:

http://download.eclipse.org/tools/mylyn/update/e3.3

Next important extension is PyDev (http://pydev.sourceforge.net). This is the URL for the remote update site:

http://pydev.sourceforge.net/updates/

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

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

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 http://community.qnx.com/sf/discussion/do/listTopics/projects.pkgsrc/discussion.general.