Skip to content

Latest commit

 

History

History
130 lines (102 loc) · 5.39 KB

INSTALL.md

File metadata and controls

130 lines (102 loc) · 5.39 KB
Raw

I. Installing 3rd-parties

sView requires several 3rd-party components for building:

On Debian/Ubuntu you might use the following command to install all dependencies at once:

sudo apt-get install \
 g++ \
 libgtk2.0-dev \
 libopenal-dev \
 libgl1-mesa-dev \
 libavcodec-dev libavdevice-dev libavformat-dev libavutil-dev libswscale-dev \
 libwebp-dev \
 libconfig++-dev libconfig-dev \
 libxpm-dev \
 codeblocks

The similar command for RPM-based distributives:

yum install gcc gcc-c++ \
 gtk+-devel gtk2-devel \
 mesa-libGLU-devel glew-devel \
 openal-devel \
 libconfig-devel

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
yum install ffmpeg-devel

On Windows and macOS please refer to official documentation for each project. Notice that DevIL and FreeImage libraries are optional and are not required for building sView (libraries are loaded dynamically if available).

II. Makefile (Linux, macOS, Android)

Current Makefile has been written only for DEB/RPM source packages and lacks configuration flexibility (means there NO any ./configure and so on).

All you need is to install dependencies and to execute traditional commands:

  make && make install

Android

sView for Android is build in two steps:

  • Building native libraries using UNIX Makefile. Paths to NDK and 3rd-party libraries can be specified through command-line options to make or by editing Makefile itself. sView does not provide .mk files - it uses UNIX Makefile for building native code.
  make android ANDROID_NDK=$SVIEW_NDK FFMPEG_ROOT=$SVIEW_FFMPEG FREETYPE_ROOT=$SVIEW_FREETYPE OPENAL_ROOT=$SVIEW_OPENAL LIBCONFIG_ROOT=$SVIEW_LIBCONFIG
  • Compiling Java classes and putting everything into APK file using Eclipse. Eclipse performs building automatically (by default), but APK file is not created by this action. APK export can be started from context menu on project sView (in the tree) -> Export -> Android -> Export Android Application. Android Studio is currently can not be used for this purpose (not tested).

This instruction has been tested only on Linux host.

III. Code::Blocks

Code::Blocks is an official way for building and development of sView. There are several building targets depending on platform (Mac OS X, Linux, Windows) and debugging possibilities:

  • WIN_vc_x86, 32-bit target using Visual Studio compiler
  • WIN_vc_AMD64_DEBUG,64-bit target with debugging options
  • WIN_vc_AMD64, 64-bit target using Visual Studio compiler
  • LINUX_gcc, Linux target, g++ compiler
  • LINUX_gcc_DEBUG, Linux target with debugging options
  • MAC_gcc, Mac OS X target, g++ compatible compiler
  • MAC_gcc_DEBUG, Mac OS X target with debugging options

Notice that the following compilers should be configured within Code::Blocks:

  • gcc, configured to g++ or compatible compiler (on systems other than Windows)
  • msvc10, configured to Visual Studio 2010+ compiler, PSDK and DXSDK
  • windows_sdk_x86_64 (copy of msvc10) configured to 64-bit libraries and compiler toolchain

3rd-parties should be either configured as Code::Blocks global compiler options or placed into "3rdparty" folder.

IV. Building options

Several preprocessor directives control building options. Notice that by default "include/stconfig.conf" file is used to override these options (this file will be used only when ST_HAVE_STCONFIG is defined).

  • ST_HAVE_WEBP - should be defined to activate libwebp usage (notice that since next releases of FFmpeg might have built-in support for webp/webpll image files)
  • ST_HAVE_MONGOOSE - should be defined to activate built-in web UI for remote Movie Player control
  • ST_DEBUG - should be defined to activate debugging log output
  • ST_DEBUG_LOG_TO_FILE - specifies file name or full path to duplicate debug log output

V. Distribution scripts

Several script were written to automate distribution routines. All them were placed in "distribution" folder.

  • build.bat, batch script for Windows. Performs re-building of WIN_vc_x86 and WIN_vc_AMD64 targets using Code::Blocks and pack result binaries using InnoSetup script. Notice that all dependencies should be available (including InnoSetup), and DLLs should be placed into bin/WIN_vc_x86 and bin/WIN_vc_AMD64 folders.
  • buildDebSrc.sh, bash script for Linux to pack sources into Debian source package.
  • buildMac.sh, bash script to pack binaries from bin/MAC_gcc folder into DMG image. 3rd-party libraries should be already located in "bin/MAC_gcc_DEBUG/sView.app/Contents/Frameworks/" folder with correct search path (refer to bind_frameworks.sh auxiliary script).
su
yum install rpm-build

mkdir -p ${HOME}/workspace/redhat/{RPMS,SRPMS,SPECS,SOURCES,BUILD}
echo "%_topdir ${HOME}/workspace/redhat" > ${HOME}/.rpmmacros

wget https://launchpad.net/~sview/+archive/stable/+files/sview_12.05-1%7Eprecise.tar.gz
mv sview_12.05-1~precise.tar.gz $HOME/workspace/redhat/SOURCES/sview_12.05-1.tar.gz
rpmbuild -ba distribution/sView.rpm.spec