Here is the 32-bit binary I compiled for Raspberry Pi. This particular build was done on stock Raspbian Buster (Debian 10 based) on a Raspberry Pi 3, but it also works on Raspberry Pi 4. Being 32-bit it probably also works on Rasberry Pi 2 and 1/Zero but I haven't tested on those.
In order to compile I installed all dependencies as a first step. Then I installed libssl1.0-dev as suggested for Debian 9 onward. I had to comment the following two lines in curecoin-qt.pro
QMAKE_CXXFLAGS += -msse2
QMAKE_CFLAGS += -msse2
since the SSE2 extension is not a feature of these ARM chips.
Afterwards I ran
qmake "USE_UPNP=-"
make
to get the executable. I was unable to compile with UPNP support and "USE_UPNP=0" also threw errors. After running and using the program however I didn't experience any connection problems. Maybe someone could take a look at why upnpDiscover function at net.cpp expects something different than what is defined.
Here is the 32-bit binary I compiled for Raspberry Pi. This particular build was done on stock Raspbian Buster (Debian 10 based) on a Raspberry Pi 3, but it also works on Raspberry Pi 4. Being 32-bit it probably also works on Rasberry Pi 2 and 1/Zero but I haven't tested on those.
In order to compile I installed all dependencies as a first step. Then I installed libssl1.0-dev as suggested for Debian 9 onward. I had to comment the following two lines in curecoin-qt.pro
since the SSE2 extension is not a feature of these ARM chips. Afterwards I ran
to get the executable. I was unable to compile with UPNP support and "USE_UPNP=0" also threw errors. After running and using the program however I didn't experience any connection problems. Maybe someone could take a look at why upnpDiscover function at net.cpp expects something different than what is defined.