ccextractor icon indicating copy to clipboard operation
ccextractor copied to clipboard
verified publisher icon CCExtractor

[BUG] Windows - cmake build is failing

Open canihavesomecoffee opened this issue 4 years ago • 1 comments

CCExtractor version: master

Necessary information

  • Is this a regression (i.e. did it work before)? YES (probably)
  • What platform did you use? Windows
  • What were the used arguments? N/A

Additional information

Building with cmake yields a "zlib.lib" missing fatal error (LNK1104) on Windows.

If we fix this, we should also extend our action workflow for windows to include cmake building.

canihavesomecoffee avatar Jun 22 '21 20:06 canihavesomecoffee

Hi @canihavesomecoffee , I’m exploring CCExtractor for GSoC 2026 and focusing on DevOps/cloud-related contributions.

Along with trying to investigate this Windows CMake build issue, I’d also love to contribute more broadly — especially around Docker, CI/CD pipelines, or improving contributor environments.

If there are specific areas or tasks where help is needed in this direction, I’d really appreciate your guidance. I’m committed to contributing consistently and aligning my work with the project’s goals.

Lavanyajc avatar Jul 29 '25 03:07 Lavanyajc

Hi! I noticed the earlier PR related to this issue was closed. Is this still unresolved and open for someone to work on, or is there an updated fix planned/under review? I’m happy to take this up and test on Windows if help is still needed.

Rahul-2k4 avatar Dec 16 '25 08:12 Rahul-2k4

Closing this issue as the Windows build is working correctly using the officially supported method (MSBuild with Visual Studio solution files).

Current status:

  • Windows CI builds are passing: https://github.com/CCExtractor/ccextractor/actions/workflows/build_windows.yml
  • The CI uses msbuild ccextractor.sln with vcpkg for dependencies

Why CMake doesn't work on Windows: The CMake configuration uses pkg_check_modules() for finding dependencies (like GPAC), which requires pkg-config - a tool that isn't standard on Windows. The CMake setup was designed for Linux/macOS.

Recommendation: For Windows builds, use the Visual Studio solution in the windows/ directory, which is the officially supported and tested method. The solution works with vcpkg for dependency management.

If there's interest in adding CMake support for Windows in the future, that would be a new feature request requiring:

  • Replacing pkg-config usage with find_package() or vcpkg toolchain integration
  • Adding Windows-specific library discovery logic

For now, the MSBuild approach is reliable and well-tested.

cfsmp3 avatar Dec 21 '25 21:12 cfsmp3