waaren wrote: ↑Monday 21 December 2020 19:30
megamarco83 wrote: ↑Monday 21 December 2020 18:37
if i will build an image with a raspberry pi (raspbian buster) this build i can share and will be compatible also with a PC that is running debian as OS ?
thanks!
I am not sure but probably not as they will have different CPU's. Easy enough to check
?
hi, i get a try to build from source in debian.
i succeed on all passage, but i have a doubt:
cd open-zwave-read-only
git pull
make # Make a note of the version information for the next steps
sudo make install
and it was:
Building OpenZWave Version 1.6-1570-ga9d57fcc - 1.6.1570
so i enter:
Code: Select all
marco@debian:~/open-zwave-read-only$ nano cpp/src/vers.cpp
and this is the file:
Code: Select all
#include "Defs.h"
uint16_t ozw_vers_major = 1;
uint16_t ozw_vers_minor = 6;
uint16_t ozw_vers_revision = 1570;
char ozw_version_string[] = "1.6-1570-ga9d57fcc";
so i continue like explained:
Code: Select all
marco@debian:~/open-zwave-read-only$ rm libopenzwave.a
marco@debian:~/open-zwave-read-only$ make
make[1]: ingresso nella directory "/home/marco/open-zwave-read-only/cpp/build"
Building OpenZWave Version 1.6-1570-ga9d57fcc - 1.6.1570
Linking Static Library
make[1]: uscita dalla directory "/home/marco/open-zwave-read-only/cpp/build"
make[1]: ingresso nella directory "/home/marco/open-zwave-read-only/cpp/examples/MinOZW"
make[1]: Nessuna operazione da eseguire per "default".
make[1]: uscita dalla directory "/home/marco/open-zwave-read-only/cpp/examples/MinOZW"
marco@debian:~/open-zwave-read-only$ make install
make[1]: ingresso nella directory "/home/marco/open-zwave-read-only/cpp/build"
Makefile:249: Documentation not being built
Installing Shared Library
cp: impossibile creare il file regolare '//usr/local/lib64//libopenzwave.so.1.6': Permesso negato
make[1]: *** [Makefile:260: install] Error 1
make[1]: uscita dalla directory "/home/marco/open-zwave-read-only/cpp/build"
make: *** [Makefile:27: install] Error 2
why i receive this error?
but ok for me is not important the support for zwave so i proceed with the wiki...
finally steps are:
Code: Select all
cd dev-domoticz
git pull
cmake -DCMAKE_BUILD_TYPE=Release CMakeLists.txt
make
i complete without issue.
now i guess that i have to synchronize domoticz folder with domoticz-dev folder
so i create this
.sh script:
Code: Select all
sudo nano update-domoticz-source.sh
and i paste this:
Code: Select all
source=~/dev-domoticz # or the directory you use(d) for development
target=~/domoticz # or another target directory
sudo mkdir -p $target/backups
sudo mkdir $target/plugins
# One of the next two rsync comamnds will copy your domoticz binary to the target location
sudo rsync -I $source/bin/domoticz $target/domoticz # will error if the binary is not in $source/bin
sudo rsync -I $source/domoticz $target/domoticz # will error if the binary is not in $source
sudo rsync -rI $source/www/ $target/www
sudo rsync -rI $source/dzVents/ $target/dzVents
sudo rsync -rI $source/Config/ $target/Config
sudo rsync -rI $source/scripts/ $target/scripts
sudo rsync -I $source/History.txt $target
sudo rsync -I $source/License.txt $target
sudo rsync -I $source/server_cert.pem $target
(not need the #!/bin/bash at begin??)
then i stop domoticz and run the bash script:
Code: Select all
marco@debian:~$ sudo service domoticz stop
marco@debian:~$ ./update-domoticz-source.sh
mkdir: impossibile creare la directory "/home/marco/domoticz/plugins": File già esistente
rsync: link_stat "/home/marco/dev-domoticz/bin/domoticz" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1207) [sender=3.1.3]
marco@debian:~$ sudo service domoticz start
why i got this error?
if i enter now in domoticz i see the last version committed: 12781
so it seams that all is working good....so why this two error: zwave and rsyn?
last question....next time that i want to compile i guess that i will have only to:
1) Build Support for OpenZWave 1.6+
2) Domoticz Source
3) Rsync script
is it correct?
the manual operation that you mention, that is the reason why the avaliable version for :
./updatebeta
is 12738
and last is 12781
it is this one:
where we have to write the version downloaded with wget command?
thanks!!!
Marco