Information for compilation needed

[peterjit]

I wanted to update to version 3.8.0 on my raspberry pi. Unfortunately the old installation page, where the process of compilation was described has moved and the new one lacks this information I know this is quite a noob question but I'd be grateful if someone could help me out here...

[jujudusud]

You can now read the compiling informations here :
https://github.com/jamulussoftware/jamulus/blob/master/COMPILING.md

[gilgongo]

@peterjit

I didn't find an arm64 .deb file for version 3.8.0

Ah OK. So it sounds like we need to amend the compile steps that are currently there to read:

make distclean # make clean on Raspberry Pi
qmake # qmake-qt5 on Fedora 33
make
sudo make install

Can anyone confirm? I have no test equipment for this.

[dcorson-ticino-com]

I use the following for my ARM headless server:

qmake "CONFIG+=nosound headless"
make
sudo make install

[jujudusud]

I use the following for my ARM headless server:

qmake "CONFIG+=nosound headless"
make
sudo make install

You also have to clean the source if the build as always been done before.
nosound and headless options are relevant only if you want to build an headless server only.
Could you please have a building test with the following:

• qmake
• make clean
• make

And tell us if there is an error somewhere ?

[dcorson-ticino-com]

I could do a client build, but can't test the result as my hardware has no head.
It is just a headless server.
I don't do the clean as I remove the sources after making the executable.

[npostavs]

make distclean works if you have run qmake before so that Makefile exists (e.g., you built the previous version, and are now doing git pull to update). If you download the sources to a new directory every time, then cleaning isn't needed.

make: *** No rule to make target 'distclean'. Stop.

This happens if you run make distclean without running qmake first. Or if you run it twice (because it deletes the Makefile). Maybe it's better to suggest make clean because it doesn't have that fails-after-the-second-time caveat.

There's nothing raspberry pi specific about it.