mirror of
https://github.com/vcmi/vcmi.git
synced 2024-12-24 22:14:36 +02:00
Updated build instructions with Fedora focus
This commit is contained in:
parent
a6151a5296
commit
c3a4f15eda
29
README.linux
29
README.linux
@ -31,43 +31,50 @@ On Debian-based systems (e.g. Ubuntu) run:
|
||||
sudo apt-get install cmake g++ libsdl1.2debian libsdl-image1.2-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev zlib1g-dev libavformat-dev libswscale-dev libboost-dev libboost-filesystem-dev libboost-system-dev libboost-thread-dev libboost-program-options-dev libboost-locale-dev qtbase5-dev
|
||||
|
||||
On RPM-based distributions (e.g. Fedora) run:
|
||||
sudo yum install cmake gcc-c++ SDL-devel SDL_image-devel SDL_ttf-devel SDL_mixer-devel boost boost-devel boost-filesystem boost-system boost-thread boost-program-options boost-locale zlib-devel ffmpeg-devel ffmpeg-libs
|
||||
sudo yum install cmake gcc-c++ SDL2-devel SDL2_image-devel SDL2_ttf-devel SDL2_mixer-devel boost boost-devel boost-filesystem boost-system boost-thread boost-program-options boost-locale zlib-devel ffmpeg-devel ffmpeg-libs
|
||||
|
||||
II. Getting the sources
|
||||
|
||||
VCMI is still in development. We recommend the following initial directory structure:
|
||||
trunk
|
||||
trunk/src -> contains sources and is under SVN control
|
||||
trunk/vcmi -> contains sources and is under git control
|
||||
trunk/build -> contains build output, makefiles, object files,...
|
||||
|
||||
You can get latest sources with subversion:
|
||||
cd trunk
|
||||
svn co http://svn.code.sf.net/p/vcmi/code/trunk/
|
||||
git clone https://github.com/vcmi/vcmi.git
|
||||
|
||||
III. Compilation
|
||||
|
||||
Run configure:
|
||||
mkdir build && cd build
|
||||
cmake ../src <any other options, see below>
|
||||
cmake ../vcmi <any other options, see below>
|
||||
|
||||
Additional options that you may want to use:
|
||||
To enable debugging: -DCMAKE_BUILD_TYPE=Debug
|
||||
To enable launcher: -DENABLE_LAUNCHER=Yes
|
||||
To change installation directory: -DCMAKE_INSTALL_PREFIX=$absolute_path_to_directory
|
||||
|
||||
Notice:
|
||||
The ../src/ is not a typo, it will place makefile scripts into the build dir
|
||||
The ../vcmi/ is not a typo, it will place makefile scripts into the build dir
|
||||
as the build dir is your working dir when calling CMake.
|
||||
|
||||
Then build vcmi:
|
||||
make -j2 (j2 = compile with 2 cpu cores, you can specifiy any value)
|
||||
make -j2 (j2 = compile with 2 threads, you can specify any value)
|
||||
|
||||
That will generate vcmiclient, vcmiserver as well as 3 .so libraries.
|
||||
That will generate vcmiclient, vcmiserver, vcmilauncher as well as 3 .so libraries.
|
||||
|
||||
III. Installing binaries
|
||||
|
||||
To install VCMI you can use "make install" command however generation of distribution-specific packages is usually a better idea. In most cases this can be achieved using tool called "checkinstall"
|
||||
|
||||
If you're compiling vcmi for development puposes, it's better to use links instead.
|
||||
If you're compiling vcmi for development puposes, the easiest is to use cmake prefix and then make install:
|
||||
|
||||
# mkdir .../trunk/install
|
||||
# cmake -DCMAKE_INSTALL_PREFIX=.../trunk/install ../vcmi
|
||||
# make && make install
|
||||
# .../trunk/install/bin/vcmiclient
|
||||
|
||||
|
||||
it's better to use links instead.
|
||||
Go to /BIN_PATH/, and type:
|
||||
|
||||
ln -s .../trunk/build/client/vcmiclient
|
||||
@ -86,5 +93,3 @@ Go to /LIB_PATH/vcmi/AI, and type:
|
||||
Go to /DATA_PATH/vcmi, and type:
|
||||
ln -s .../trunk/source/config
|
||||
ln -s .../trunk/source/Mods
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user