Setting up a portable C++ project still is a pain in the ass, especially if it shall be portable.
...
Export our example from public svn:
| No Format |
|---|
# for a anflat application project: svn export "https://svn.clazzes.org/svn/pba/trunk/pba-helloworld-portable" $MYAPPNAME # for a multi-module multi-program application project: svn export "https://svn.clazzes.org/svn/pba/trunk/pba-hellobigworld-portable" $MYAPPNAME # for a library project: svn export "https://svn.clazzes.org/svn/pba/trunk/pba-hellolib-portable" $MYAPPNAME |
...
| No Format |
|---|
# Variant 1: Remove NSIS installer only. For libraries common despite cross compilation. rm -rf nsis src/*.nsi # Variant 2: Remove all windows crossbuilding stuff rm -rf nsis src/*.nsi src/include-mingw.mk 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:
| No Format |
|---|
$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
...
| No Format |
|---|
make -C nsis && ls -ltr nsis/*.exe |
Optional multi-module/multi-program variant: Create Modules, Programs
| No Format |
|---|
# create module common
scripts/create_module.sh common
# create program foobar-daemon
scripts/create_program.sh 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:
| No Format |
|---|
# Debug
${ProjDirPath}/build/unix/debug
# Release
${ProjDirPath}/build/unix/release
# Win32
${ProjDirPath}/build/win32/release
# Win64
${ProjDirPath}/build/win64/release |