Open ewhac opened 1 year ago
CPack's DEB generator is not capable of generating Debian packages. IIRC it can only generate .deb
files compatible with Ubuntu because it does not conform to Debian package standards.
To create Debian-compliant packages there is an entire separate project for it (https://gitlab.kitware.com/debian/dh-cmake) to somehow create them.
We officially only provide support for Ubuntu and Flatpak, so that's what the codebase will provide out of the box. Any adjustments/changes required for other distributions need to be done locally or provided by the specific packagers.
If you find an issue that makes it impossible to package OBS Studio for Debian manually, we can revisit those issues.
We officially only provide support for Ubuntu and Flatpak, so that's what the codebase will provide out of the box. Any adjustments/changes required for other distributions need to be done locally or provided by the specific packagers.
make package
was very convenient and, up until a couple of month ago, worked just fine even on a "vanilla" Debian system. If this is OBS's official position, then it should drop from the READMEs and CMakefiles the pretense of supporting building .deb or .rpm packages.
We officially only provide support for Ubuntu and Flatpak, so that's what the codebase will provide out of the box. Any adjustments/changes required for other distributions need to be done locally or provided by the specific packagers.
make package
was very convenient and, up until a couple of month ago, worked just fine even on a "vanilla" Debian system. If this is OBS's official position, then it should drop from the READMEs and CMakefiles the pretense of supporting building .deb or .rpm packages.
That's fair criticism - we've only just begun laying out some clearer rules and limitations for the project, so it's an ongoing process. It was clarified here:
https://github.com/obsproject/obs-studio/pull/9597#issuecomment-1721748505
We don't officially provide support outside of:
- Windows 10 [1]
- Windows 11 [1]
- macOS 11+ [1]
- Ubuntu 22.04+ [2]
- Flatpak
[...]
As those are our primary concerns, we tend to align our code, CMake included, with that list. For other platforms, such as FreeBSD, Debian, CentOS, or Fedora, we tend to prefer having packagers patch on their build systems for their own platform requirements unless it is prohibitively difficult or impossible to do so. Otherwise, we're at the mercy of everyone needing their own changes upstreamed because of their constraints.
That obviously does not mean that use on other distributions will be intentionally broken, but in this specific case it means that we don't implement a package
target for Linux outside of CMake's DEB
generator (and it is that generator does not support Debian, which we have no power over).
We haven't changed any code related to the CPack generator in the 6-week timeframe you've mentioned though, so this could be related to any module we build.
Could you post the cmake
invocation you used to build the project and upload a TXT file with the complete error output of cpack
?
Could you post the
cmake
invocation you used to build the project and upload a TXT file with the complete error output ofcpack
?
I usually use the interactive ccmake
and tweak the build opts by hand. I've attached the output of cmake -L ..
from the build directory, as well as the full output from cpack
(version 3.27.7).
From what I can tell the root cause is that ./usr/local/lib/obs-scripting/_obspython.so
is looking for usr/local/lib/libobs-frontend-api.so.0
, but what's actually installed is ./usr/local/lib/libobs-frontend-api.so.30
.
I wonder how this could happen as the frontend api is built with the correct SOVERSION in the build tree and there should not be a version with version 0. Are you using a fresh build directory?
Are you using a fresh build directory?
I tried creating a fresh build directory, but the result was the same.
Operating System Info
Other
Other OS
Debian Sid
OBS Studio Version
Git
OBS Studio Version (Other)
No response
OBS Studio Log URL
-na-
OBS Studio Crash Log URL
No response
Expected Behavior
The command
make package
orcpack
should generate installable Debian package files.Current Behavior
Package build fails in
dpkg-shlibdeps
:The files that are claimed to have no dependency information change between runs. A run subsequent to the above reported:
This same build environment worked fine up until about six weeks ago. Creating a new build directory from scratch did not help.
Steps to Reproduce
git pull --recurse-submodules
make -j11
make package
Anything else we should know?
ENABLE_BROWSER
is false. Full debug output fromcpack
available upon request (4800 lines, 163KB).