40ca86a17290994d56f98fcd0e97c661c2a09f60
This change makes it possible to create a MacOSX app bundle of either Debug or Release builds: * The script setup/MacOSX/bundle_install.sh is configured by cmake to be placed in the apps Debug and Release folders. * Execution of bundle_install.sh creates the bundle file structure and copies binaries, libs, frameworks and resources into it. * The script uses install_name_tool to reconfigure the dynamic library paths and framework paths of the binary, so they won't point to the system libraries, but to the locations in the bundle instead. * An Info.plist file is also configured by cmake and placed in the bundle by the script. Note: It is named bundle_info.plist in the Debug and Release folders after configuration so the start of the binary during developement does not use it. * When opening the bundle it is assured via setup() in src/app/platform_includes/includesMac.h that the working directory of the binary is set to .app/Contents/Resources so the paths to the data files are evaluated correctly. fortune cookie message = Dein Einsatz wird in Kürze belohnt werden.
Masterproject
Setup
External Software
- QT 5.2.1
- CxxTest 4.3
- Valgrind 3.9.0(linux, macOS)
- Clang & LLVM (installation guide http://clang.llvm.org/docs/LibASTMatchersTutorial.html)
- Boost 1.55 ()
Environment Variables
- QT_DIR - ...\Qt\Qt5.2.1\5.2.1<IDE>\
- CXX_TEST_DIR - .../cxxtest-4.3/
- CLANG_DIR - .../clang-llvm/
- BOOST_155_DIR - .../boost_1_55_0
For Win32:
- VLD_DIR - .../Visual Leak Detector
Settings
Run setup script: $ ./script/setup.sh
Languages
C++
63.4%
Java
32.7%
CMake
1.6%
Shell
1.1%
CSS
0.6%
Other
0.4%