Here is my experience with 1.27 on Ubuntu 13.10 building from source:
The week 1.27 was released I had 1.26.5 up and running.
I cloned the 1.27 master from github and merged the mysql2PDO branch into it.
I used the cmakecacheimport script to generate a cache file then used cmake to build the package using this command:
Code: Select all
cmake -C zm_conf.cmake . -DZM_CGIDIR="/usr/lib/cgi-bin" -DZM_CONTENTDIR="/media/JW_2TB_1/zm" -DZM_PERL_SUBPREFIX="/usr/share/perl5" -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_VERBOSE_MAKEFILE=ON
when I tried to make the build I got the following error:
Code: Select all
Only one of PREFIX or INSTALL_BASE can be given. Not both.
make: *** [scripts/ZoneMinder/CMakeFiles/zmperlmodules] Error 255
make: *** [scripts/ZoneMinder/CMakeFiles/zmperlmodules.dir/all] Error 2
make: *** [all] Error 2
I was able to get around this by running make as root.
I then installed it and got ZM up and running after using zmupdate.pl to upgrade the db.
I was able to view monitors and motion detection was working but I noticed that the events were not being listed on the main index page. This has since been solved as reported here: https://github.com/ZoneMinder/ZoneMinder/issues/364
By this time the Iconnor branch had merged the mysql2PDO fix into it so I decided to checkout the Iconnor branch and build it the same way, however cmake failed do to undefined functions relating to something called Fifostream:: which I couldn't find any information on. I'm guessing I'm missing a dependency.
I then attempted to once again build the master with mysql2PDO and the commit to fix the event listings. I was able to make and install, however none of my monitors would display.
The logs showed zm not being able to access shared memory, and a whole bunch of socket_sento errors and sock files not being found. I tried all the fixes for these types of errors list on the internet but had no luck getting around them.
I've resorted to reverting back to 1.26.5 for the time being, which using the same cmake command to configure works perfectly. Not sure where to go from here, but plan on continuing to try to build 1.27 and get it running.