-
Notifications
You must be signed in to change notification settings - Fork 19
Build instructions
Currently, there are three ways to compile Saddy:
- On Windows, using Microsoft Visual C++ 2010
- On Windows, using MinGW
- On Linux, using GCC
If you want to use atlasgen tool (Ruby version), make sure that Ruby installed with devil and json gem.
If you want to compile atlsasgen, exporter or IFaceEd make sure, that Qt 4.8 included (Qt 5 is supported too). To build IFace Editor in Ubuntu, using Qt5, please install qtscript5-dev package (besides having Qt5 installed of course)
If you want to compile all or freetype plugin, make sure that FREETYPE_INCLUDE and FREETYPE_LIB is set to corresponsing locations on Windows. Please configure FREETYPE_INCLUDE and FREETYPE_LIB paths to point to include and library files for Freetype library. An example for FREETYPE_INCLUDE path: C:\Program Files\GnuWin32\include\freetype2
Make sure, that your freetype include folder contains ft2build.h file, ftconfig.h at the top. If not - copy them from inner subfolders, where freetype is installed.
If you want to compile all or irrklang plugin, make sure, that IRRKLANG_ROOT is set to point to irrklang location. This applies both for Linux and Windows. In case of x32 architecture IRRKLANG_ROOT must point to main irrklang folder (not the folder with __MACOSX prefix). In case of x64 architecture please rename bin/linux-gcc-64 subfolder to bin/linux-gcc in IrrKlang folder.
For MSVC, run Qt command prompt, used to run with MSVC, change folder to where Saddy is located and type build-all-msvc.bat Debug for debug build, or build-all-msvc.bat Release for release build.
For MinGW, run Qt command prompt, used to run with MinGW, change folder to where Saddy is located and type build-all-mingw.bat Debug for debug build, or build-all-mingw.bat Release for release build.
For Linux, using GCC, change folder to where Saddy is located in terminal and type build-all-linux-gcc.sh Debug for debug build, or build-all-linux-gcc.sh Release for release build.
For MSVC, every subproject (plugin, example, test) has a solution or project or attached to it. You can use it to build a project.
For MinGW, every subproject (plugin, example, test), except for ones using Qt, has corresponsing executable debug.bat or release.bat to build it
For Linux, using GCC every subproject (plugin, example, test), except for ones using Qt, has corresponsing executable debug.sb or release.bat to build it
For Qt-based subprojects use qmake.
Saddy has a tool for creating texture mapped fonts (exporter). See exporter folder in plugins. It uses Qt as a backend.
Also it has a tool for creating texture atlases. See atlasgen (for Ruby as backend) or atlasgenc (for Qt as backend)