Latest Bookwom build errors with RTSP

[mryel00]

Bookworm packages just got updated and liblivemedia-dev is now missing RTSPServerSupportingHTTPStreaming.hh.

output/rtsp/rtsp.cc:28:10: fatal error: RTSPServerSupportingHTTPStreaming.hh: No such file or directory
   28 | #include <RTSPServerSupportingHTTPStreaming.hh>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

It seems like RTSPServerSupportingHTTPStreaming got already removed in 2020 according to the changelog:
http://www.live555.com/liveMedia/public/changelog.txt

2020.04.06:

• Removed support for the classes “RTSPServerSupportingHTTPStreamingâ€� and "TCPStreamSinkâ€�.
  These were being used (in the "LIVE555 Media Server") for streaming using
  "HTTP Live Streaming" (HLS). This was always a hack; it is better to use a dedicated
  HTTP server to serve HLS segments, rather than trying to implement a HTTP server
  (serving 'virtual HLS segments) within our own (primarily RTSP) server.

  If you are looking for HLS support, note that we provide a source-code demo application
  "testH264VideoToHLSSegments" that converts a (static) H.264 Elementary Stream file to
  HLS segments, and the "LIVE555 HLS Proxy", which proxies a live RTSP/RTP stream
  to HLS segments.

Therefore I would think camera-streamer used some deprecated code that got finally removed.
This is just a guess and no fact ofc. I don't have deep knowledge about the source code.

Without a rewrite of the source code someone can run make USE_RTSP=0 or make USE_RTSP=0 -j<number_of_cores> to build on the latest Bookworm.

edit: with camera-streamer 0.3.0 RTSP gets disabled automatically if it cannot find RTSPServerSupportingHTTPStreaming.hh

[nogoer]

saw your response to my comment on #188 and yes this is more specific to my comment having the same issue. There seems to be increasing issues with camera-streamer compiling correcting and this is the most recent. I researched for hours and never stumbled on this though, just other past issues like 177 and 188.

[mryel00]

This is a different repo. This here is the camera-streamer repo, the issue you replied to was on the Crowsnest repo.
The latest Crowsnest issue with camera-streamer not building is this one: mainsail-crew/crowsnest#297
The one before that is this one: mainsail-crew/crowsnest#278
Your reply was to the first ever issue with Bookworm when Bookworm was just released and development didn't catch up yet.

Those two issues I linked were pretty simple bugs that I was able to fix on my own, or someone else made the groundwork and I adjusted it to be backwards compatible.
This time it's not the case that I can fix it, so we will have to wait for @ayufan or someone else to fix RTSP again.

[nogoer]

This is a different repo. This here is the camera-streamer repo, the issue you replied to was on the Crowsnest repo. The latest Crowsnest issue with camera-streamer not building is this one: mainsail-crew/crowsnest#297 The one before that is this one: mainsail-crew/crowsnest#278 Your reply was to the first ever issue with Bookworm when Bookworm was just released and development didn't catch up yet.

Those two issues I linked were pretty simple bugs that I was able to fix on my own, or someone else made the groundwork and I adjusted it to be backwards compatible. This time it's not the case that I can fix it, so we will have to wait for @ayufan or someone else to fix RTSP again.

ah ok, now i see the issue is known. Im a dev, albeit not python or linux and i dont have repo access but im not sure i know the history to make a fix either.

[mryel00]

A few things that bothered me in your message, sry if it sounds rude and I don't want to kick off a discussion about this here:
Don't cite the whole message, if it's directly above yours and only cite the things that are needed for context. Your way of citing does not give any additional context and just leads to longer mails and more to scroll.

Im a dev, albeit not python or linux

Luckily for you camera-streamer is written in C and C++. You don't really need Linux knowledge to fix this problem.
If you have knowledge about C++ programming and about the RTSP protocol, then you can try to fix it and I think a lot of people would appreciate it.

i dont have repo access

You don't need repo access or push rights for this repo. As this is open source you can create a fork, fix it and then create a PR, like this one #169. I don't have any rights on this repo either.

This said, I don't think that you have the knowledge to fix this issue, as you wrote yourself. We will have to wait for someone else to pick this up and to make their life easier, we should not unnecessarily write further unrelated things.

[nogoer]

i just did a reply quote, normal behavior, but no offence taken. This issue is more about missing libraries than it is a code issue. The simple fix could simply involve including the legacy rtsp files in the current repo and fixing the paths. The more complicated fix would be to merge the rtsp code into the camera library so it doesnt need the legacy code. The long term fix is recoding the camera-streaming library to natively use rtsp or remove it if its obsolete. Not sure why the pi os no longer has it. Also not sure if im on base since i know almost nothing about the core functionality of this library.

[rongith]

Thank you for mryel00@4c390f5
Set USE_RTSP ?= 0 in Makefile saved my latest compilation.
Done.

[ayufan]

You can do make USE_RTSP=0 as of now.

…

On Thu, 26 Jun 2025 at 14:13, rongith ***@***.***> wrote: *rongith* left a comment (ayufan/camera-streamer#177) <#177 (comment)> Thank you for ***@***.*** <mryel00@4c390f5> Set USE_RTSP ?= 0 in Makefile saved my latest compilation. Done. — Reply to this email directly, view it on GitHub <#177 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASOSQM37WCY667WYX7ZZ5D3FPPW7AVCNFSM6AAAAACABRQ7VSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBYGI3TKMZWGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mryel00]

@ayufan I saw #178 thank you for that.

For clarification of future plans:
Do you intend to add a new RTSP implementation in future yourself, or do you intend to just drop it unless someone else contributes an implementation?

[ayufan]

I intend to add it back. This was the lowest possible way to not fail builds.

[mryel00]

Should I close this then? As the initial error is fixed, or should I keep it open to track the RTSP implementation?

[ayufan]

I think creating separate issue to bring back RTSP support would be better. As the compilation error at least now is fixed.

[ayufan]

Created the #182