Building Moondust Project from sources

From Moondust Wiki
Jump to navigation Jump to search

This is a special manual where will be written about building process for each operating system.

Common Preparation

  • Download sources (clone dev repo)
  • Download any config pack

First of all, you will need to download all sources:

Try to clone the repository by those commands: 

#make directory for your repos if you haven't it
mkdir ~/myrepos
cd ~/myrepos/

#clone repo into your new directory
git clone https://github.com/Wohlhabend-Networks/PGE-Project.git
cd PGE-Project
git submodule update --init --recursive

(for Windows you can use Git Bash, included with git installation)

But if you failed to clone repo, you also can download sources as ZIP:

https://github.com/Wohlhabend-Networks/PGE-Project

(use the link "Download Zip" for getting the sources from GitHub)

Then download dependent next sumbodules and put them into their folders (Without those submodules PGE is not build-able!):

https://github.com/Wohlhabend-Networks/PGE-File-Library-STL, PGE File Library, must be in "_common/PGE_File_Formats" folder.


And after download any configuration package (which contains graphics, music and sounds) which need to be able work with PGE:

http://wohlsoft.ru/config_packs.php

Note: Don't forget place configs, languages (after built *.qm files) directories with compiled executable file!

Building for Linux

Dependences

Need to install

  • Qt >= 5.4 (You can download it here: http://www.qt.io/download-open-source/ (You need the "Open Source" version)
  • gcc >=4.7
  • g++ >=4.7
  • Installed OpenGL libraries and headers (mesa-drv, x11-xcb-dev, etc.)

Already included with PGE sources (there are will be built by build_deps.sh script)

  • SDL2 2.3 (used latest version from official Mercurial repository)
  • SDL Mixer X (a.k.a. SDL2_mixer_ext) - fork of SDL2 mixer made by Wohlstand
    • libogg
    • libvorvis
    • libFLAC
    • libMAD
    • libmodplug (sources are merged with SDL Mixer X)
    • libADLMIDI (recoded into library from ADLMIDI console player)
    • libGME
  • FreeImageLite (modded FreeImage which supports PNG, BMP, GIF and ICO formats only. Purpose of mod - reduce library size with disabled of useless for PGE format libraries)
  • libluabind (deboostified version)
    • luajit (based on Lua 5.2)

Note: italic dependencies are partially modified (fixed warnings or some bugs)

Installing of development tools

GCC and system libraries

Install gcc and dependent libraries on Debian/Ubuntu/Mint

For modern releases 

sudo apt-get install gcc g++ make git wget
sudo apt-get install build-essential
sudo apt-get install libasound2-dev libdbus-1-dev libegl1-mesa-dev libgl1-mesa-dev libgles2-mesa-dev libglu1-mesa-dev libmirclient-dev libpulse-dev libsndio-dev libudev-dev libwayland-dev libx11-dev libxcursor-dev libxext-dev libxi-dev libxinerama-dev libxkbcommon-dev libxrandr-dev libxss-dev libxt-dev libxv-dev libxxf86vm-dev

For older releases 

sudo apt-get install gcc g++ make git wget
sudo apt-get install build-essential
sudo apt-get install "^libxcb.*" libx11-dev libx11-xcb-dev libxcursor-dev libxrender-dev \
libxrandr-dev libxext-dev libxi-dev libxss-dev libxt-dev libxv-dev \
libxxf86vm-dev libxinerama-dev libxkbcommon-dev libfontconfig1-dev \
libasound2-dev libpulse-dev libdbus-1-dev libts-dev udev mtdev-tools webp \
libudev-dev libglm-dev libwayland-dev libegl1-mesa-dev mesa-common-dev \
libgl1-mesa-dev libglu1-mesa-dev libgles2-mesa libgles2-mesa-dev

Optional: you can install a ccache tool to use it for speed-up building process 

sudo apt-get install ccache

on Redhat / CentOS 

sudo yum install gcc g++ make git wget nano
sudo yum install alsa-lib-devel libX11-devel libXScrnSaver-devel libXcursor-devel libXext-devel libXi-devel libXinerama-devel libXrandr-devel libXrender-devel libxkbcommon-devel mesa-libEGL-devel mesa-libGL-devel mesa-libGLES-devel mesa-libGLU-devel systemd-devel

on openSUSE 

sudo zypper install gcc gcc-c++ make git wget nano
sudo zypper install alsa-lib-devel libX11-devel libXScrnSaver-devel libXcursor-devel libXext-devel libXi-devel libXinerama-devel libXrandr-devel libXrender-devel libxkbcommon-devel mesa-libEGL-devel mesa-libGL-devel systemd-devel

Qt 5

To get Qt installation you have two ways: you can install Qt5 packages from your repositories but also you can download it here:

http://www.qt.io/download-open-source/

Note: You can see more download links if you will open "View all downloads" page.

If you download necessary package from official site, you should open Terminal and set "executable" permission to get able start installation.

  • download package to your PC
wget http://download.qt-project.org/official_releases/online_installers/qt-opensource-linux-x64-online.run
  • Set executable:
chmod u+x qt-opensource-linux-x64-1.6.0-4-online.run
  • Run installer:
./qt-opensource-linux-x64-1.6.0-4-online.run

and follow install instructions.

after installation don't forget to check installed Qt (If your Qt was installed into "/opt/Qt/"): 

/opt/Qt/5.6/gcc_64/bin/qmake -v

If you will get message like this: 

QMake version 3.0
Using Qt version 5.6.0 in /opt/Qt/5.5.1/gcc_64/lib

Everything are okay ;-)

for convenience, you can make symlink to qmake in the /usr/bin and use qmake easier: 

sudo ln -s /opt/Qt/5.6/gcc_64/bin/qmake /usr/bin/qmake

Warning! If you have already installed other versions of Qt you can create symlink, for example, with "qmake-qt5" name

Preparing for build

  • Extract the source code to a folder where you can find it easily (for example, /home/vasya/projects/pge/)
  • Extract the downloaded config pack into /path/to/your/source/Content/configs

You must have this tree:

  • open the terminal and change current directory to the unpacked folder with project sources
  • run the generate_paths.sh file and when gedit will open, type the paths to qmake and to lrelease (in the bin directory of your Qt,

for example /opt/Qt/5.6/gcc_64/bin/qmake, /opt/Qt/5.6/gcc_64/bin/lrelease)

  • run the build_deps.sh to build included dependent libraries.

Building code

To build project use the special build.sh script: 

chmod u+x build.sh
./build.sh

When everything will be built, you will see a built executables in the ./bin folder.

To start usage of the editor, run the pge_editor file

Additional arguments of build.sh

  • no-pause - skips pause on script finishing
  • use-ccache - can speed-up building process, but you need to install ccache tool. Works with GCC compiler.

Deploying of built stuff

If you wish to pack your build to use it on another computers without rebuilding, you can run the "deploy_linux.sh" script from a "_Misc/dev_scripts/deploy" folder: 

cd _Misc/dev_scripts/deploy
./deploy_linux.sh
cd ../../..

When deploy script will finish it's job, you will get the "bin/_packed/pge-project-dev-linux-mint.tar.gz" file which you can share to friends or use on another computers yourself.

Notes:

  • Your build will work on compatible linux distros only: I.e. PGE built on Debian/Mint/*Ubuntu will NOT work on Fedora/CentOS/Redhat/OpenSUSE or back!
  • To have right deployment, you should build PGE with Static version of Qt.

Building for Windows

Dependences

  • MinGW >= 4.9 (You can get MinGW installer here: http://sourceforge.net/projects/mingw/files/latest/download?source=files) (MinGW already includes with Qt MinGW installer)
  • Qt >= 5.4 (You can download it here: http://www.qt.io/download-open-source/#section-5) (Get Qt for Windows 32 bit (minGW) or use Online Installer to take same version. Don't download VisualStudio versions if you don't plan to use it for yourself! PGE requires MinGW, because MinGW has support of a functions used by PGE which are not available in MSVC!)
  • 7zip (You can download it here: http://7-zip.org/) (needed for deploy script which must be used with dynamic Qt build which available to download)
  • Git (You can download it here: https://git-scm.com/) (Optionally, without it PGE Editor/Engine are will have not build-ID mark in about dialog)
  • SDL2 >= 2.0 (Already included in the _Libs/_builds/win32)
  • SDL2_mixer >= 2.0 (Already included in the _Libs/_builds/win32)

Installation of the development tools

Install all the tools in a folder, for example, C:\DevTools.

  • MinGW into C:\MinGW (if you got it separated)
  • Qt into C:\Qt

Qt installation Note: you must enable those components:

  • 5.6.0 -> MinGQ 4.9.2 32 bit or similar
  • Tools -> MinGW 4.9.2 or similar

Other components are optional and doesn't required

After the install, you can add MinGW and Qt directories into PATH environment:

(if tools was installed into C:\DevTools, you must append those folders into PATH global variable) 

C:\MinGW\bin
C:\MinGW\msys\1.0\bin
C:\MinGW\lib
C:\MinGW\msys\1.0\lib

to use your installed MinGW separately or 

C:\Qt\Tools\mingw492_32\bin
C:\Qt\Tools\mingw492_32\lib

to use the internal pre-installed MinGW in the Qt folder

PATH string to append: 

;C:\Qt\5.6\mingw49_32\bin;C:\Qt\Tools\mingw492_32\bin

Preparing to build

  • Extract the source code to a folder where you can find it easily (Path shouldn't contain non-ASCII characters!)
  • Extract the downloaded config pack into /path/to/your/source/Content/configs or into /path/to/your/source/bin-w32/configs (if bin-w32 and configs sub-directory are not exists - create them!)

You must have this tree:

  • run the generate_paths.bat file and when notepad will open, type the paths to Qt and to MinGW

for example C:\Qt\5.6\mingw49_32\bin and C:\Qt\Tools\mingw492_32\bin)

  • run the build_deps.bat to build included dependent libraries.

Build code

  • In the project folder, hold Shift key on your keyboard and press the right mouse button, and in the context menu select "Open command window" (available for Windows 7 and newer).
  • In the opened command Window, enter these commands for the build:
build.bat

If everything is successfully built, you will see the built PGE executables in the bin-w32 subfolder - it's the compiled PGE application. You can run and use it!

P.S. If you was built the dynamic version, you need to run the "_Misc\dev_scripts\deploy\deploy_windows_dynamic.bat" script to automatically copy necessary DLLs into PGE's binary folder. You need to have installed 7zip to have able run this script.

When everything is built, you can run the pge_editor.exe from a bin-w32 directory to run editor application or run the pge_engine.exe to launch game engine.

Building for Mac OS X

Dependences

Installing of development tools

XCode

To install XCode you need to download it from your App Store.

Dependent tools

To have correct working build scripts, you also need to install "coreutols", "binutils" and "gnu-sed" 

brew install coreutils
brew install binutils
brew install gnu-sed

Note: If you are using MacPorts, do those commands instead: 

port install bunutils
port install coreutils
port install gsed

Qt

You have two ways to install Qt:

  • via homebrew in with terminal command: brew install qt5
  • via Online installer (We recommends you to choice the ~/Qt path which will be easy to access from Finder)

Important Note for El Capitan (OS X 10.11.*)

If you received a build errors with missing of the headers which a small bug which forces to find SDK for OS X 10.10 while you have pre-installed SDK only for 10.11. This trouble can be easily fixed with a small workaround: you will need to make a symlink to 10.11 in the SDK's folder: 

ln -s /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk \
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk

Since you will run this in the terminal, build process must work correctly

Static version of Qt

If you don't want to have a troubles with frameworks and dependent dynamic libraries, we are recommending to build static version of Qt yourself. Here is detail manual how to build static version of Qt 5 for Mac OS X: Building static Qt 5

Preparing to build

  • Extract the source code to a folder where you can find it easily (Path shouldn't contain non-ASCII characters!)
  • Extract the downloaded config pack into /path/to/your/source/Content/configs

You must have this tree:

  • run the generate_paths.sh file and when nano will open, add Qt path into environment and save file with CMD+O

for example ~/Qt/clang_32/bin)

  • run the build_deps.sh to build included dependent libraries.

Building code

To build project use the special build.sh script: 

./build.sh

When everything will be built, you will see the built app bundles in the ./bin folder.

To start usage of the editor, run the pge_editor.app file

Deploying of built stuff

If you wish to make a DMG image to use your build on another computers without rebuilding, you can run the "deploy_osx.sh" script from a "_Misc/dev_scripts/deploy" folder: 

cd _Misc/dev_scripts/deploy
./deploy_osx.sh
cd ../../..

When deploy script will finish it's job, you will get the "bin/_packed/pge-project-dev-macosx.dmg" file which you can share to friends or use on another computers yourself.

Note: To have right deployment, you should build PGE with Static version of Qt.

Links

Retrieved from "https://wohlsoft.ru/wiki/index.php?title=Building_Moondust_Project_from_sources&oldid=3587"