ffmpeg-build-script Building sratom fails on Ubuntu 22.04 (LV2 issue)

trafficstars

I originally installed this back in 88d49833e1c86d44fdec7f2731ea48988c3d2995 and it worked great!

However, I just tried to update and got this error.

python3 ./waf configure --prefix=/home/sjw/git/ffmpeg-build-script/workspace --static --no-shared
$ python3 ./waf
Build commands will be stored in build/compile_commands.json
Waf: Entering directory `/mnt/storage/sjw/git/ffmpeg-build-script/packages/sratom-v0.6.8/build'
[1/3] Compiling src/sratom.c
[2/3] Compiling sratom.pc.in
In file included from ../src/sratom.c:17:
../include/sratom/sratom.h:24:10: fatal error: lv2/atom/atom.h: No such file or directory
   24 | #include "lv2/atom/atom.h"
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.

Waf: Leaving directory `/mnt/storage/sjw/git/ffmpeg-build-script/packages/sratom-v0.6.8/build'
Build failed
 -> task in 'libsratom_static' failed with exit status 1 (run with -v to display more information)

I thought it might be an issue with build artifacts so I deleted the directory and re-cloned it but still no dice.

I haven't really done anything with the system aside from just keeping it updated.

I did a git checkout 88d49833e1c86d44fdec7f2731ea48988c3d2995
Then a ./build-ffmpeg --build --enable-gpl-and-non-free
It gave an error about zlib
Updated the zlib download URL
Ran ./build-ffmpeg --build --enable-gpl-and-non-free again
Same error as before

Maybe the issue is LV2?

apt list lv2-dev
>not installed
well_there_it_is
sudo apt install lv2-dev

Okay, let's try this again! ./build-ffmpeg --build --enable-gpl-and-non-free
it_works
git checkout master
>error about stashing my changes
Oh right, I updated the URL for zlib
git checkout master --force
./build-ffmpeg --build --enable-gpl-and-non-free
It builds without issue!
great_success

I've no clue how LV2 got removed. The only thing I can think of is if it was somehow removed by a system update.

In which case maybe have the script check for lv2-dev and install it if needed or specifically list it as a dependency and include it with the code snippet to install the dependencies.

Or maybe it was just an issue with my system for some reason. In which case I guess this issue can at least serve as a remedy for anyone else in the same boat ⛵