[BUG] Windows - cmake build is failing #649

New Issue

claunia · 2026-01-29T16:50:08Z

claunia commented

2026-01-29 16:50:08 +00:00

Originally created by @canihavesomecoffee on GitHub (Jun 22, 2021).

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.

Originally created by @canihavesomecoffee on GitHub (Jun 22, 2021). 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.

claunia added the bug help wanted Hacktoberfest labels 2026-01-29 16:50:08 +00:00

claunia closed this issue

2026-01-29 16:50:09 +00:00

claunia commented

2026-01-29 16:50:09 +00:00

@Lavanyajc commented on GitHub (Jul 29, 2025):

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 commented on GitHub (Jul 29, 2025): 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.

claunia commented

2026-01-29 16:50:10 +00:00

@Rahul-2k4 commented on GitHub (Dec 16, 2025):

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 commented on GitHub (Dec 16, 2025): 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.

claunia commented

2026-01-29 16:50:10 +00:00

@cfsmp3 commented on GitHub (Dec 21, 2025):

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 commented on GitHub (Dec 21, 2025): 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.

claunia referenced this issue

2026-01-29 17:16:45 +00:00

[PR #649] [MERGED] Fix defects #1491

claunia referenced this issue

2026-01-29 17:16:45 +00:00

[PR #649] Fix defects #1496

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ccextractor#649