147 lines
12 KiB
Plaintext
147 lines
12 KiB
Plaintext
Installing ZoneMinder with cmake
|
|
--------------------------------
|
|
Starting with ZoneMinder 1.26.4, ZoneMinder can now be installed using cmake. This requires cmake version 2.6 or newer.
|
|
cmake is an alternative to the autotools collection (libtool, autoconf, automake, autoheader and such). Its more recent and has many advantages, including, but not limited to:
|
|
* One program (cmake) instead of multiple. (libtool, autoconf, automake, etc)
|
|
* One file per directory (CMakeLists.txt) instead of multiple. (configure.ac, Makefile.am and sometimes more)
|
|
* One syntax (cmake's syntax) instead of multiple. (bash and m4)
|
|
* Generation of makefiles for many platforms, including Windows.
|
|
* Newer than autotools and is being actively developed.
|
|
* Generates colored makefiles with progress indicator.
|
|
* Slightly faster because its based on C and not bash.
|
|
* Lots of documentation, unlike autotools: http://www.cmake.org/cmake/help/cmake2.6docs.html
|
|
|
|
At this point, its still possible to use autotools for the ZoneMinder project. Choosing cmake or autotools is now a matter of preference.
|
|
Hopefully in the future, cmake will become the default way to install ZoneMinder.
|
|
|
|
Important differences
|
|
---------------------
|
|
* Unlike the autotools way, the cmake way does not require any options. It attempts to detect some things by its own (system directories, libarch, web user and group) and uses defaults for others (installation paths and such).
|
|
* Unlike the autotools way, which links the binaries to a fixed list of libraries, the cmake way only links to libraries that it found on the system. If a library is not found, but required, a fatal error will be shown during the configuration step.
|
|
* Unlike the autotools way, the cmake way does not modify the system in any way it shouldn't. It only does what its supposed to do: Install files to your system. Nothing else and nothing leaks out of the DESTDIR environment variable (if used). This means that depending on your configuration, there might be an extra required step after installation: to link WEB_PATH/events and WEB_PATH/images folders to the correct places.
|
|
|
|
Configuration
|
|
-------------
|
|
cmake by default does not require any parameters, but its possible to override the defaults with the options below.
|
|
|
|
Configuration can be done in 4 ways:
|
|
1) As a command line parameter, e.g. cmake -DCMAKE_VERBOSE_MAKEFILE=ON .
|
|
2) Using cmake-gui
|
|
3) Providing cmake with an initial cache file with the -C option
|
|
IMPORTANT: Do not use the -C option if any major part of your system, excluding the version of zoneminder, has changed.
|
|
For example, do not use this option if: you have upgraded your distro to a new version, have gone from 32 to 64 bits,
|
|
or have migrated from one machine to another.
|
|
4) By editing the cache file CMakeCache.txt (after it has been generated) - Not recommended
|
|
|
|
Possible configuration options:
|
|
ZM_RUNDIR Location of transient process files, default: /var/run/zm
|
|
ZM_SOCKDIR Location of Unix domain socket files, default /var/run/zm
|
|
ZM_TMPDIR Location of temporary files, default: /tmp/zm
|
|
ZM_LOGDIR Location of generated log files, default: /var/log/zm
|
|
ZM_WEBDIR Location of the web files, default: <prefix>/share/zoneminder/www
|
|
ZM_CGIDIR Location of the cgi-bin files, default: <prefix>/libexec/zoneminder/cgi-bin
|
|
ZM_CONTENTDIR Location of dynamic content (events and images), default: /var/lib/zoneminder
|
|
ZM_DB_HOST Hostname where ZoneMinder database located, default: localhost
|
|
ZM_DB_NAME Name of ZoneMinder database, default: zm
|
|
ZM_DB_USER Name of ZoneMinder database user, default: zmuser
|
|
ZM_DB_PASS Password of ZoneMinder database user, default: zmpass
|
|
ZM_WEB_USER The user apache or the local web server runs on. Leave empty for automatic detection. If that fails, you can use this variable to force
|
|
ZM_WEB_GROUP The group apache or the local web server runs on, Leave empty to be the same as the web user
|
|
ZM_DIR_EVENTS Location where events are recorded to, default: ZM_CONTENTDIR/events
|
|
ZM_DIR_IMAGES Location where images, not directly associated with events, are recorded to, default: ZM_CONTENTDIR/images
|
|
ZM_DIR_SOUNDS Location to look for optional sound files, default: sounds
|
|
ZM_PATH_ZMS Web url to zms streaming server, default: /cgi-bin/nph-zms
|
|
Advanced:
|
|
ZM_PATH_MAP Location to save mapped memory files, default: /dev/shm
|
|
ZM_PATH_ARP Full path to compatible arp binary. Leave empty for automatic detection.
|
|
ZM_CONFIG_DIR Location of the main ZoneMinder config file, zm.conf. default: /etc/zm
|
|
ZM_CONFIG_SUBDIR Location of custom config files. default: ZM_CONFIG_DIR/conf.d
|
|
ZM_EXTRA_LIBS A list of optional libraries, separated by semicolons, e.g. ssl;theora
|
|
ZM_MYSQL_ENGINE MySQL engine to use with database, default: InnoDB
|
|
ZM_NO_MMAP Set to ON to not use mmap shared memory. Shouldn't be enabled unless you experience problems with the shared memory. default: OFF
|
|
ZM_NO_FFMPEG Set to ON to skip ffmpeg checks and force building ZM without ffmpeg. default: OFF
|
|
ZM_NO_X10 Set to ON to build ZoneMinder without X10 support. default: OFF
|
|
ZM_PERL_MM_PARMS By default, ZoneMinder's Perl modules are installed into the Vendor folders, as defined by your installation of Perl. You can change that here. Consult Perl's MakeMaker documentation for a definition of acceptable parameters. If you set this to something that causes the modules to be installed outside Perl's normal serach path, then you will also need to set ZM_PERL_SEARCH_PATH accordingly. default: "INSTALLDIRS=vendor NO_PACKLIST=1 NO_PERLLOCAL=1"
|
|
ZM_PERL_SEARCH_PATH Use to add a folder to your Perl's search path. This will need to be set in cases where ZM_PERL_MM_PARMS has been modified such that ZoneMinder's Perl modules are installed outside Perl's default search path. default: ""
|
|
|
|
Useful configuration options provided by cmake:
|
|
CMAKE_VERBOSE_MAKEFILE - Set this to ON (default OFF) to see what cmake is doing. Very useful for troubleshooting.
|
|
CMAKE_BUILD_TYPE - Set this to Debug (default Release) to build ZoneMinder with debugging enabled.
|
|
CMAKE_INSTALL_PREFIX - Use this to change the prefix (default /usr/local). This option behaves like --prefix from autoconf. Package maintainers will probably want to set this to "/usr".
|
|
|
|
Useful environment variables provided by cmake:
|
|
CMAKE_INCLUDE_PATH - Use this to add to the include search path.
|
|
CMAKE_LIBRARY_PATH - Use this to add to the library search path.
|
|
CMAKE_PREFIX_PATH - Use this to add to both include and library search paths. <path>/include will be added to the include search path and <path>/lib to the library search path. Multiple paths can be specified, separated by a : character. For example: export CMAKE_PREFIX_PATH="/opt/libjpeg-turbo:/opt/ffmpeg-from-git"
|
|
|
|
CFLAGS, CPPFLAGS and other environment variables:
|
|
To append to the CFLAGS and CXXFLAGS, please use the CFLAGS and CXXFLAGS environment variables.
|
|
Or use the CMAKE_C_FLAGS and CMAKE_CXX_FLAGS configuration options.
|
|
To replace the CFLAGS and CXXFLAGS entirely:
|
|
* For the Release build type: use CMAKE_C_FLAGS_RELEASE for the CFLAGS and CMAKE_CXX_FLAGS_RELEASE for the CXXFLAGS
|
|
* For the Debug build type: use CMAKE_C_FLAGS_DEBUG for the CFLAGS and CMAKE_CXX_FLAGS_DEBUG for the CXXFLAGS
|
|
Other important environment variables (such as LDFLAGS) are also supported.
|
|
|
|
The DESTDIR environment variable is also supported, however it needs to be set before invoking make install. For example: DESTDIR=mydestdir make install
|
|
For more information about DESTDIR, see:
|
|
* http://www.gnu.org/prep/standards/html_node/DESTDIR.html
|
|
|
|
Basic steps for installing ZoneMinder on a fresh system
|
|
-------------------------------------------------------
|
|
1) After installing all the required dependencies, in the project directory, run "cmake [extra options] ."
|
|
This behaves like ./configure. It is also possible to supply configuration options, e.g. cmake -DZM_DB_PASS="mypass" .
|
|
IMPORTANT: Don't forget the dot "." at the end.
|
|
2) Run "make" to compile ZoneMinder
|
|
3) Run "make install" (as root, or use sudo) to install ZoneMinder to your system.
|
|
4) Create a directory for the content and the necessary symlinks by running zmlinkcontent.sh with the directory you want to use. e.g. ./zmlinkcontent.sh /nfs/zm
|
|
5) Create a database for zoneminder, called "zm".
|
|
6) Create a user for the zoneminder database, called zmuser with password and full privileges to the "zm" database.
|
|
NOTE: The database server, database name, user and password can be different and adjusted during configuration step with the options in this file, or by editing /etc/zm.conf
|
|
7) Populate the zoneminder database using the script zm_create.sql. This should be found in <prefix>/share/zoneminder/db or in the project/db directory.
|
|
|
|
8) Create an apache virtual host for ZoneMinder. Make sure to use the same paths as ZM_WEBDIR and ZM_CGIDIR in /etc/zm.conf
|
|
9) Verify date.timezone is set to your timezone. This parameter is often found inside the system php.ini file. Consult your distribution's documentation for the proper way to set this value.
|
|
10) Create other config if desired (e.g. rsyslog, logrotate and such). Some of this can be found in <prefix>/share/zoneminder/misc or project/misc directory
|
|
11) Setup an appropriate startup script for your system. Two generic startup scripts have been provided, a legacy Sys V Init script and a Systemd service file.
|
|
|
|
*Sys V Init Setup*
|
|
- Copy the sys v init script /scripts/zm from the build folder to /etc/init.
|
|
- Inspect the contents to make sure they apply to your distro.
|
|
|
|
*SystemD Setup*
|
|
- Copy the zoneminder systemd service file /misc/zoneminder.service from the build folder to the systemd service file location.
|
|
For Redhat based distros, that folder is /usr/lib/systemd/system.
|
|
- Inspect the contents to make sure they apply to your distro.
|
|
- Tell systemd to load the new service file: "sudo systemctl daemon-reload".
|
|
- Copy /misc/zoneminder-tmpfiles.conf to /etc/tmpfiles.d
|
|
- Tell systemd to process this file: "sudo /usr/bin/systemd-tmpfiles --create /etc/tmpfiles.d/zoneminder.conf".
|
|
|
|
Basic steps for upgrading ZoneMinder
|
|
------------------------------------
|
|
1) If you wish to use the same paths and configuration as the currently installed ZoneMinder, you need to provide cmake with options that match your current installation.
|
|
You can provide those options in the command line to cmake, e.g. cmake -DZM_DB_PASS="blah" -DZM_WEBDIR="/usr/local/share/zoneminder/www" -DCMAKE_INSTALL_FULL_BINDIR="/usr/bin" .
|
|
Or alternatively, for convenience, use the cmakecacheimport.sh script. This reads a zoneminder configuration file (zm.conf) and creates a cmake initial cache file called zm_conf.cmake, which you can then provide to cmake.
|
|
For example:
|
|
./cmakecacheimport.sh /etc/zm.conf
|
|
cmake -C zm_conf.cmake [extra options] .
|
|
|
|
2) Run "make" to compile ZoneMinder
|
|
3) Run "make install" (as root, or use sudo) to install ZoneMinder to your system.
|
|
4) Depending on your configuration: If the DIR_EVENTS and DIR_IMAGES options are set to default (pointing to web directory/events and web directory/images), You will need to update the symlinks in the web directory to the correct folders. e.g. web directory/events should point to the real events directory, and likewise for the images directory.
|
|
You can use the zmlinkcontent.sh script for this. For example, if /var/lib/zoneminder is the folder that contains the "images" and "events" directories, you can use:
|
|
./zmlinkcontent.sh /var/lib/zoneminder
|
|
By default, the content directory for new installations is /var/lib/zoneminder. This can be overridden in cmake with the ZM_CONTENTDIR option. e.g. cmake -DZM_CONTENTDIR="/some/big/storage/zm" .
|
|
|
|
5) Run zmupdate.pl to update the database layout to the new version.
|
|
|
|
Uninstallation:
|
|
---------------
|
|
By default, cmake does not have an uninstall target, however we have added a one. Simply run make uninstall (or DESTDIR=mydestdir make uninstall if a DESTDIR was used) and it will remove all the files that cmake installed.
|
|
It's also possible to do this manually. The file install_manifest.txt contains the list of files installed to the system. This can be used in many ways to delete all files installed by cmake, such as: xargs rm < install_manifest.txt
|
|
|
|
Contributions:
|
|
--------------
|
|
Please visit our GitHub at http://github.com/ZoneMinder/ZoneMinder
|
|
|
|
|