obsproject/obs-studio

OBS Studio 30.1.0-beta1 FTBFS on NixOS due to a sign-compare warning in QSV_Encoder_Internal.cpp

Open

#10,200 建立於 2024年2月4日

在 GitHub 查看
 (12 留言) (0 反應) (0 負責人)C (72,387 star) (9,239 fork)batch import
Good first issueplatform/linux

描述

Operating System Info

Other

Other OS

NixOS 23.11

OBS Studio Version

30.1.0-beta1

OBS Studio Version (Other)

No response

OBS Studio Log URL

This is a build failure, so no runtime logs are available

OBS Studio Crash Log URL

No response

Expected Behavior

OBS Studio 30.1.0-beta1 should compile successfully.

Current Behavior

OBS Studio 30.1.0-beta1 FTBFS due to a sign-compare warning being raised as an error. Here is the error from the build logs.

obs-studio> /build/source/plugins/obs-qsv11/QSV_Encoder_Internal.cpp:337:50: error: comparison of integer expressions of different signedness: 'int' and 'const uint32_t' {aka 'const unsigned int'} [8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wsign-compare-Werror=sign-compare8;;]
obs-studio>   337 |             (pParams->nWidth * pParams->nHeight) >= pixelcount_4k) {

Steps to Reproduce

  1. Use NixOS 23.11
  2. Create a local package for libdatachannel 0.20.1 (example)
  3. Create a local package for OBS Studio 30.1.0-beta1 (example)
  4. nix build .#obs-studio -L

Anything else we should know?

Line 337 that raises the warning was introduced in this commit:

The build can be coerced to complete successfully by passing -Wno-error=sign-compare to cmake.

貢獻者指南

技術棧
cppc
領域
desktopbuild system
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic C++ knowledgeunderstanding of compiler warningsfamiliarity with cmake
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
The issue is a sign compare warning in plugins/obs qsv11/QSV Encoder Internal.cpp at line 337. The warning occurs because (pParams >nWidth * pParams >nHeight) is int and pixelcount 4k is uint32 t. A simple cast or change of variable type should fix it. The commit that introduced the issue is 2874b8f1cc81736e22e75494ffc8a76bdc8a8969. The build can be coerced by passing Wno error=sign compare to cmake, but a proper fix is preferred.