Child pages
  • PBA-cbs bootstrapping of portable C++ project
Skip to end of metadata
Go to start of metadata

Setting up a portable C++ project still is a pain in the ass, especially if it shall be portable.

When trying to automate it in some way, we came to the conclusion that a full example in a public subversion repository is a good solutions because it's easy to use for you and easy to maintain for us.

HowTo ...

These are the steps for an ultra fast bootstrapping of a portable project relying on pba-cbs and our incarnation of the MinGW cross compilation toolchain.


You need deb sources for pba (any-pba-1.0) and distro-mingw-5 (i.e. squeeze-mingw-5 or wheezy-mingw-5), see

For starters, You need to install the packages pba-cbs and subversion.

Retrieve the sceleton

Decide for the main name of your app:


Export our example from public svn:

# for a flat application project:
svn export "" $MYAPPNAME

# for a multi-module multi-program application project:
svn export "" $MYAPPNAME
# for a library project:
svn export "" $MYAPPNAME
Rename and search'n'replace

Rename some stuff and have the inlcude files adapted:

scripts/ $MYAPPNAME
rm scripts/
Optional: Remove windows stuff

If you do not want windows binaries, remove it:


# Variant 1: Remove NSIS installer only. For libraries common despite cross compilation.
rm -rf nsis src/*.nsi

# Variant 2: Remove NSIS installer and mingw-5
rm -rf nsis src/*.nsi debian-mingw-5
# Variant 3: Remove all windows crossbuilding stuff
rm -rf nsis src/*.nsi src/ src/*.rc debian-mingw* build/win*
$EDITOR build/Makefile
Adapt debian package meta infos

Change my name and e-mail to yours and adapt the description:

$EDITOR debian*/control debian*/changelog $(ls -1 src/*.pc.tmpl src/*.rc src/*.nsi src/*.h 2>/dev/null)

Do not forget to change the icon, too!

Update or remove the ReadMe

At least remove the link to this page ...

# edit ...
$EDITOR doc/ReadMe.txt
# ... or remove the file and the reference in debian*/rules
rm doc/ReadMe.txt
$EDITOR debian*/rules
Optional: Activate svn or another revision control system

Now (and before any build activity) is a very good time to put your project under subversion control:

svn add `pwd`

You might also want to fill svn:ignore properties of some directories:

Optional: Install required libs and build the package

To produce the debian packages, just:

# this needs sudo privileges
pba-builddeps -i
pba-build -u

# or dpkg-build*

To only build the linux packages or only the windows packages, add -o unix resp. -o mingw to the pba-commands.

Optional: Create Windows Installers

(Re)edit the .nsi script template and replace all instances of "" with something of your choice:

$EDITOR src/*.nsi

Then "make" the nsis directory:

make -C nsis && ls -ltr nsis/*.exe
Optional multi-module/multi-program variant: Create Modules, Programs
# create module common
scripts/ common
# create program foobar-daemon
scripts/ foobar-daemon

Eclipse Hints

To create the Ecplise project, select File, New, Project..., C/C++, Makefile Project with existing code.

The recommended Build Configurations and their Build directories are:

# Debug
# Release
# Win32
# Win64
  • No labels