Fix raspijamulus #2267

corrados · 2022-01-23T15:00:16Z

Short description of changes
raspijamulus.sh did not work for newest Raspbian OS.

Context: Fixes an issue?
Missing install packets, new jack2 version needed.

Does this change need documentation? What needs to be documented and how?
No.

Status of this Pull Request
Unforunately, the current Jamulus source code does not compile on my Raspberry Pi with the following error message:

src/util.cpp: In static member function ‘static bool NetworkUtil::ParseNetworkAddress(QString, CHostAddress&, bool)’:
src/util.cpp:708:28: error: variable ‘QRegularExpression rx1’ has initializer but incomplete type
  708 |     QRegularExpression rx1 ( "^\\[([^]]*)\\](?::(\\d+))?$" ); // [addr4or6] or [addr4or6]:port
      |                            ^
src/util.cpp:709:28: error: variable ‘QRegularExpression rx2’ has initializer but incomplete type
  709 |     QRegularExpression rx2 ( "^([^:]*)(?::(\\d+))?$" );       // addr4 or addr4:port or host or host:port
      |                            ^
src/util.cpp:713:29: error: variable ‘QRegularExpressionMatch rx1match’ has initializer but incomplete type
  713 |     QRegularExpressionMatch rx1match = rx1.match ( strAddress );
      |                             ^~~~~~~~
src/util.cpp:714:29: error: variable ‘QRegularExpressionMatch rx2match’ has initializer but incomplete type
  714 |     QRegularExpressionMatch rx2match = rx2.match ( strAddress );
      |                             ^~~~~~~~
make: *** [Makefile:1762: util.o] Error 1

What is missing until this pull request can be merged?
The above compilation error is independent of this pull request.

Checklist

I've verified that this Pull Request follows the general code principles
I tested my code and it does what I want
My code follows the style guide
I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
I've filled all the content above

softins · 2022-01-23T17:27:28Z

Hi Volker, nice to see you here again!

I recently updated my Pi to the latest Raspberry Pi OS, and Jamulus still compiles fine. Here is my OS version:

tony@pi:~ $ cat /etc/issue
Raspbian GNU/Linux 11 \n \l

tony@pi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

The Qt packages I have installed are:

tony@pi:~ $ apt list qt\* --installed
Listing... Done
qt3d5-doc/stable,now 5.15.2+dfsg-2+rpi1 all [installed,automatic]
qt5-assistant/stable,now 5.15.2-5 armhf [installed,automatic]
qt5-doc/stable,now 5.15.2-2 all [installed]
qt5-gtk-platformtheme/stable,now 5.15.2+dfsg-9+rpi1 armhf [installed,automatic]
qt5-gtk2-platformtheme/stable,now 5.0.0+git23.g335dbec-4+rpt1 armhf [installed,automatic]
qt5-qmake-bin/stable,now 5.15.2+dfsg-9+rpi1 armhf [installed,automatic]
qt5-qmake/stable,now 5.15.2+dfsg-9+rpi1 armhf [installed]
qt5-qmltooling-plugins/stable,now 5.15.2+dfsg-6+rpi1 armhf [installed,automatic]
qt5-style-plugin-cleanlooks/stable,now 5.0.0+git23.g335dbec-4+rpt1 armhf [installed,automatic]
qt5-style-plugin-motif/stable,now 5.0.0+git23.g335dbec-4+rpt1 armhf [installed,automatic]
qt5-style-plugin-plastique/stable,now 5.0.0+git23.g335dbec-4+rpt1 armhf [installed,automatic]
qt5-style-plugins/stable,now 5.0.0+git23.g335dbec-4+rpt1 armhf [installed,automatic]
qt5ct/stable,now 1.1-1+rpt1 armhf [installed,automatic]
qtattributionsscanner-qt5/stable,now 5.15.2-5 armhf [installed,automatic]
qtbase5-dev-tools/stable,now 5.15.2+dfsg-9+rpi1 armhf [installed,automatic]
qtbase5-dev/stable,now 5.15.2+dfsg-9+rpi1 armhf [installed,automatic]
qtbase5-doc/stable,now 5.15.2+dfsg-9+rpi1 all [installed,automatic]
qtcharts5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtchooser/stable,now 66-2 armhf [installed,automatic]
qtconnectivity5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtcreator-data/stable,now 4.14.1-1 all [installed]
qtcreator-doc/stable,now 4.14.1-1 all [installed]
qtcreator/stable,now 4.14.1-1 armhf [installed]
qtdatavisualization5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtdeclarative5-dev-tools/stable,now 5.15.2+dfsg-6+rpi1 armhf [installed,automatic]
qtdeclarative5-dev/stable,now 5.15.2+dfsg-6+rpi1 armhf [installed]
qtdeclarative5-doc/stable,now 5.15.2+dfsg-6+rpi1 all [installed,automatic]
qtgraphicaleffects5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtlocation5-doc/stable,now 5.15.2+dfsg-2 all [installed,automatic]
qtmultimedia5-doc/stable,now 5.15.2-3 all [installed,automatic]
qtnetworkauth5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtquickcontrols2-5-doc/stable,now 5.15.2+dfsg-2 all [installed,automatic]
qtquickcontrols5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtscript5-doc/stable,now 5.15.2+dfsg-2 all [installed,automatic]
qtscxml5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtsensors5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtserialbus5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtserialport5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtsvg5-doc/stable,now 5.15.2-3 all [installed,automatic]
qttools5-dev-tools/stable,now 5.15.2-5 armhf [installed]
qttools5-doc/stable,now 5.15.2-5 all [installed,automatic]
qttranslations5-l10n/stable,now 5.15.2-2 all [installed,automatic]
qtvirtualkeyboard5-doc/stable,now 5.15.2+dfsg-2 all [installed,automatic]
qtwayland5-doc/stable,now 5.15.2-3 all [installed,automatic]
qtwebchannel5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtwebengine5-doc/stable,now 5.15.2+dfsg-3 all [installed,automatic]
qtwebsockets5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtwebview5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtx11extras5-doc/stable,now 5.15.2-2 all [installed,automatic]
qtxmlpatterns5-dev-tools/stable,now 5.15.2-3 armhf [installed,automatic]
qtxmlpatterns5-doc/stable,now 5.15.2-3 all [installed,automatic]

Maybe something is missing on your Pi?

softins · 2022-01-23T17:30:21Z

Although I only compile using qmake Jamulus.pro && make clean && make, and not using the script distributions/raspijamulus.sh. I don't know if that makes a difference; I'll have to try it.

ann0see · 2022-01-23T18:47:52Z

Hi Volker! Great to see you again.
Hope you’re fine.

Concerning the error you’ve mentioned, does this occur independently of your changes? If yes, probably it’s better to have a separate issue.

ann0see · 2022-01-23T20:49:49Z

I think this should probably be in 3.8.2?

hoffie · 2022-01-23T22:20:59Z

Hi Volker, great to see you here! :)

As far as I understand, this PR provides improvements/updates for the raspijamulus.sh script, so it basically fixes compatibility with latest (2021-10-30?) Raspbian versions, right?

In addition, you've encountered a compile error, right? I've opened issue #2272 (+ PR #2273) for the latter to keep this PR focussed on the proposed changes.

corrados · 2022-01-24T16:43:59Z

Thanks for your immediate response. First, it is a pleasure for me to see that the Jamulus project is in such a good shape. Many thanks (again) for you to organize and manage the project so well :-).

The reason I am using the raspijamulus script is that I have build a prototype hardware for my new project Edrumulus which is an open source e-drum trigger module. I am using a microprocessor (ESP32) running the Edrumulus software and a Raspberry Pi 3B+ running Drumgizmo and Jamulus at the same time. Here is a picture of that prototype:

I recently updated my Pi to the latest Raspberry Pi OS, and Jamulus still compiles fine.
[...]
Although I only compile using qmake Jamulus.pro && make clean && make, and not using the script distributions/raspijamulus.sh. I don't know if that makes a difference; I'll have to try it.

The normal qmake Jamulus.pro && make clean && make works fine for me, too.

Concerning the error you’ve mentioned, does this occur independently of your changes?

At least the correct Raspbian packages needed to be installed. The package qt5-default was not found in the current Raspbian OS.

this PR provides improvements/updates for the raspijamulus.sh script, so it basically fixes compatibility with latest (2021-10-30?) Raspbian versions, right?

Yes, this is the purpose.

In addition, you've encountered a compile error, right? I've opened issue #2272 (+ PR #2273) for the latter to keep this PR focussed on the proposed changes.

Thank you. And you already have a fix, that was quick! :-)

BTW: In the raspijamulus script I was using a custom OPUS library because it was compiled with fixed point which gave me some speed improvements on my old Raspberry Pi Zero back in the days: ./configure --enable-custom-modes --enable-fixed-point. I can see that you have added a section in the Jamulus.pro file like, e.g., :

jamulus/Jamulus.pro

Line 1159 in 2501880

QMAKE_EXTRA_COMPILERS += sse_cc sse2_cc sse4_cc

Does this mean that the normal Jamulus compilation now uses fixed point on ARM by default? Or is this just using SSE extensions which cannot be used on ARM?

softins · 2022-01-24T17:18:11Z

distributions/raspijamulus.sh

@@ -5,7 +5,7 @@ OPUS="opus-1.3.1"
 NCORES=$(nproc)

 # install required packages
-pkgs='alsamixergui build-essential qt5-default libasound2-dev cmake libglib2.0-dev'
+pkgs='alsamixergui build-essential qt5-qmake qtdeclarative5-dev qttools5-dev-tools libjack-jackd2-dev cmake libglib2.0-dev'


I have just tried this script on a Pi with fresh install of Raspbian 10 (which has Qt 5.11.3). I found that it still needs qt5-default and libasound2-dev:

without libasound2-dev, the build of jack2 fails

without qt5-default, the build of Jamulus fails.
I know that qttools5-dev-tools is needed for Qt >= 5.12 to provide lrelease.
And I have just seen your comment that qt5-default is not in Raspbian 11 (I was just about to try it myself). Interesting... it would be good if we could make this script work on both OS versions.

without libasound2-dev, the build of jack2 fails

I have just found this is also true on Raspbian 11, so libasound2-dev must still be included.

Interesting. It did compile fine on my Raspbian. But maybe I had this package libasound2-dev was already installed. I'll do some more tests and update the PR, soon.

Adding libasound2-dev is no problem because it is available. But since qt5-default is not available and cannot be installed, running the raspijamulus script will always ask Do you want to install missing packages? but if you answer with yes you'll get

Package qt5-default is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'qt5-default' has no installation candidate

The idea was that the script simply runs without interaction as soon as it was once installing everything.

Ups... I just noticed another thing which was incorrect (it's a very long time ago when I was initially writing this script): Since we checkout our own version of jack2 and compile it, we also use the headers and libraries from that location and do not use the system jack2-dev files. So, I also removed the libjack-jackd2-dev again. Sorry for the inconvenience...

One thing I have found when running this script on a fresh OS (same on both 10 and 11), is that when Jamulus compilation is finished, and the script runs Jamulus, it complains that it cannot connect to or start a jack server, and suggests starting jackd manually.

You need to have an USB audio card connected when you start the script. It takes the first device it finds (ADEVICE=$(aplay -l|grep "USB Audio"|tail -1|cut -d' ' -f3)) and tells you as an output what device it found and wants to use: echo "Using USB audio device: ${ADEVICE}". I assume that in your case no audio device was found and therefore the jack daemon could not be started.

softins · 2022-01-24T18:15:11Z

BTW: In the raspijamulus script I was using a custom OPUS library because it was compiled with fixed point which gave me some speed improvements on my old Raspberry Pi Zero back in the days: ./configure --enable-custom-modes --enable-fixed-point. I can see that you have added a section in the Jamulus.pro file like, e.g., :

jamulus/Jamulus.pro

Line 1159 in 2501880

QMAKE_EXTRA_COMPILERS += sse_cc sse2_cc sse4_cc

Does this mean that the normal Jamulus compilation now uses fixed point on ARM by default? Or is this just using SSE extensions which cannot be used on ARM?

I think it is just SSE, but I am not certain. The SSE stuff was added by @npostavs back in February.

softins · 2022-01-24T18:22:34Z

I have just done a standard compile after a make distclean, and I can see that there is no ./configure step for the OPUS libs included in the Jamulus tree, before they start to be compiled. So presumably they are being compiled with the default configuration that is already there, and might not be optimised for the particular system?

corrados · 2022-01-24T18:26:56Z

The way I integrated the OPUS library was to include all the OPUS sources and compile it together with all the other Jamulus source file. The original ./configure of the OPUS library was therefore not used. So, I assume that the normal Jamulus compilation does not use an optimized OPUS build and therefore it makes sense to keep the custom OPUS library creation in the raspijamulus script.

softins · 2022-01-24T20:34:55Z

The way I integrated the OPUS library was to include all the OPUS sources and compile it together with all the other Jamulus source file. The original ./configure of the OPUS library was therefore not used. So, I assume that the normal Jamulus compilation does not use an optimized OPUS build and therefore it makes sense to keep the custom OPUS library creation in the raspijamulus script.

I suppose the question then is: what compilation defines get set up by ./configure --enable-custom-modes --enable-fixed-point, and could those be replicated in the Jamulus.pro setup appropriately for RPi?

npostavs · 2022-01-24T20:37:34Z

I think it is just SSE, but I am not certain. The SSE stuff was added by @npostavs back in February.

Yes, basically I added the arch-specific optimizations into the Jamulus qmakefile. The referenced line is just for x86/64, but for arm I enabled NEON intrinsics (I don't really know if/how it works, but the #defines are there, as far as I know). I didn't try to enable fixed-point.

jamulus/Jamulus.pro

Lines 714 to 717 in 2501880

    
           contains(QT_ARCH, armeabi-v7a) | contains(QT_ARCH, arm64-v8a) { 
        
               HEADERS_OPUS += $$HEADERS_OPUS_ARM 
        
               SOURCES_OPUS_ARCH += $$SOURCES_OPUS_ARM 
        
               DEFINES_OPUS += OPUS_ARM_PRESUME_NEON=1 OPUS_ARM_PRESUME_NEON_INTR=1

corrados · 2022-01-25T06:21:34Z

Actually, I would not change anything in the Jamulus.pro file to support fixed-point OPUS. For most of the Jamulus use cases it is not needed. Just for very special cases like running Jamulus on a Raspberry Pi Zero, you will see a small improvement in speed if using a fixed-point OPUS library. And exactly for these special cases there is the raspijamulus script which can be used. This uses an external OPUS library which is configured with fixed-point support.

softins · 2022-01-26T11:51:57Z

I have studied and tested this on both Raspbian 10 and 11, with the aim of making the script compatible with both. This is what I have found:

On 10, the package qt5-default does two main things: pull in qtbase5-dev as a dependency, and set the default version of Qt for qtchooser. Without this, there is no default version.
On 11, the package qt5-default does not exist. qtbase5-dev is still available as the main package to install, and the default version of Qt for qtchooser is automatically set to 5 by one of the installed dependencies.
Using qtchooser -list-versions is an OS-independent way of determining whether there is already a default or qt5-default is required.
Package qtdeclaractive5-dev is not required at all, as it only provides modules not used by Jamulus.
Package qttools5-dev-tools is available on both 10 and 11, and is required on 11 to provide lrelease for qmake.

So I would recommend the following section of code for installing packages on both 10 and 11 (I have tested on fresh installs of both):

# install required packages
pkgs='alsamixergui build-essential qtbase5-dev qttools5-dev-tools libasound2-dev cmake libglib2.0-dev'
if ! dpkg -s $pkgs >/dev/null 2>&1; then
  read -p "Do you want to install missing packages? " -n 1 -r
  echo
  if [[ $REPLY =~ ^[Yy]$ ]]; then
    sudo apt-get install $pkgs -y
    # Raspbian 10 needs qt5-default; Raspbian 11 doesn't need or provide it
    if ! qtchooser -list-versions | grep -q default; then
      sudo apt-get install qt5-default -y
    fi
  fi
fi

I have a version with this change at https://github.com/softins/jamulus/tree/fix-pi

… headers and libraries for Jamulus compilation

corrados · 2022-01-26T15:50:03Z

Thanks Tony for your effort. I really like your solution.
I tried to merge your changes but I had some Git issues so that my branch is now in an invalid state. Please do not merge.

# Conflicts: # distributions/raspijamulus.sh

corrados · 2022-01-26T16:03:42Z

I think I have fixed my Git issue. Now it's ready for merge.

Package qtdeclaractive5-dev is not required at all, as it only provides modules not used by Jamulus.

I took the required packages from the COMPILING.md file from section "On Ubuntu-based distributions 18.04+, Debian 9+, and Raspberry Pi OS:". Maybe this should be updated, too.

ann0see · 2022-01-26T16:07:48Z

Yes. And probably the CI too.

softins

Great, thanks!

hoffie

Looks good to me, thanks!

CHANGELOG: Build: Raspijamulus build script has been improved to work with the latest Raspberry Pi OS releases and to include a newer JACK version.

corrados changed the title ~~Corrados fix raspijamulus~~ Fix raspijamulus Jan 23, 2022

hoffie mentioned this pull request Jan 23, 2022

Compile error with CONFIG+="headless": src/util.cpp: variable ‘QRegularExpression rx1’ has initializer but incomplete type #2272

Closed

softins reviewed Jan 24, 2022

View reviewed changes

softins added this to the Release 3.8.2 milestone Jan 26, 2022

corrados added 5 commits January 26, 2022 16:41

fix some install packets

7ae0bc8

we need a newer jack2 version, otherwise it will not compile anymore

64f3e14

added missing install packet

2d2330d

added libasound2-dev again since it is needed for jack2 compilation

ba78bfb

remove libjack-jackd2-dev since in the script we use our custom jack2…

00374c6

… headers and libraries for Jamulus compilation

Make RPi script compatible with both OS 10 and 11

dae7b7d

# Conflicts: # distributions/raspijamulus.sh

softins approved these changes Jan 26, 2022

View reviewed changes

softins requested a review from hoffie January 26, 2022 17:55

hoffie approved these changes Jan 26, 2022

View reviewed changes

hoffie merged commit f1022da into jamulussoftware:master Jan 26, 2022

ann0see mentioned this pull request Jan 26, 2022

Update documentation to use correct Linux dependencies #2289

Closed

softins mentioned this pull request Mar 31, 2022

Improve COMPILING, CONTRIBUTING and TRANSLATING files #2561

Merged

5 tasks

This pull request was closed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix raspijamulus #2267

Fix raspijamulus #2267

corrados commented Jan 23, 2022 •

edited by hoffie

Loading

softins commented Jan 23, 2022

softins commented Jan 23, 2022

ann0see commented Jan 23, 2022 •

edited

Loading

ann0see commented Jan 23, 2022

hoffie commented Jan 23, 2022 •

edited

Loading

corrados commented Jan 24, 2022

softins Jan 24, 2022

softins Jan 24, 2022

corrados Jan 24, 2022

corrados Jan 24, 2022

corrados Jan 24, 2022

softins Jan 24, 2022

corrados Jan 24, 2022

softins commented Jan 24, 2022

softins commented Jan 24, 2022

corrados commented Jan 24, 2022

softins commented Jan 24, 2022

npostavs commented Jan 24, 2022

corrados commented Jan 25, 2022

softins commented Jan 26, 2022

corrados commented Jan 26, 2022

corrados commented Jan 26, 2022

ann0see commented Jan 26, 2022

softins left a comment

hoffie left a comment

Fix raspijamulus #2267

Fix raspijamulus #2267

Conversation

corrados commented Jan 23, 2022 • edited by hoffie Loading

Checklist

softins commented Jan 23, 2022

softins commented Jan 23, 2022

ann0see commented Jan 23, 2022 • edited Loading

ann0see commented Jan 23, 2022

hoffie commented Jan 23, 2022 • edited Loading

corrados commented Jan 24, 2022

softins Jan 24, 2022

Choose a reason for hiding this comment

softins Jan 24, 2022

Choose a reason for hiding this comment

corrados Jan 24, 2022

Choose a reason for hiding this comment

corrados Jan 24, 2022

Choose a reason for hiding this comment

corrados Jan 24, 2022

Choose a reason for hiding this comment

softins Jan 24, 2022

Choose a reason for hiding this comment

corrados Jan 24, 2022

Choose a reason for hiding this comment

softins commented Jan 24, 2022

softins commented Jan 24, 2022

corrados commented Jan 24, 2022

softins commented Jan 24, 2022

npostavs commented Jan 24, 2022

corrados commented Jan 25, 2022

softins commented Jan 26, 2022

corrados commented Jan 26, 2022

corrados commented Jan 26, 2022

ann0see commented Jan 26, 2022

softins left a comment

Choose a reason for hiding this comment

hoffie left a comment

Choose a reason for hiding this comment

corrados commented Jan 23, 2022 •

edited by hoffie

Loading

ann0see commented Jan 23, 2022 •

edited

Loading

hoffie commented Jan 23, 2022 •

edited

Loading