-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu Docker fails during install step for 'cppwinrt' #712
Comments
/opt/build64/toolchain/cppwinrt-prefix/src/cppwinrt-stamp/cppwinrt-install-*.log plz I guess it's just a network problem. |
So maybe it's because wget doesn't exist? I'm not sure if these dependencies automatically pull wget in. |
That solved it! Thank you. I'm almost there but I'm running into an error at the last hurdle. docker-build-log.txt |
This issue is caused by OOM. For historical reasons, the parallel build mechanism of this script is suboptimal: there is no “global thread pool.” For example, on a 16-core system, Ninja performs 16 external projects simultaneously by default, and each external project tells Ninja/Make to emit 16 instances of the compiler, which in the worst case can result in 256 instances. This is fine for Clang, because Clang emits "cc1" in-process. However, GCC's driver and cc1 are separate executables, which can lead to hundreds of processes being created simultaneously and immediately exhaust all RAM. As far as I know, Ninja does not yet support the GNU Make jobserver protocol, so we cannot fundamentally fix this issue. However, you can switch to Clang, or limit the top-level Ninja parallelism with |
Thank you! With your help I've finally managed to 'successfully' build a windows executable.
|
You need to add
This is a GCC 14 false positive, you can add mpv-winbuild-cmake/packages/mpv.cmake Line 56 in 9c153bc
To replace it with a different source, just replace GIT_REPOSITORY, and if your branch name is not master, specify GIT_TAG and GIT_REMOTE_NAME. mpv-winbuild-cmake/packages/mpv.cmake Line 25 in 9c153bc
Just add it after CONFIGURE_COMMAND. |
I've tried: but it's failing to run the configure command. There's an error log generated that I haven't been able to look at due to issues with Docker. Presumably though I'm just not setting the argument correctly. (EDIT : my mistake, I had included an extra feature in the configure command without installing the prerequsites and this was causing it to fail) Also the previous successful build was closing immediately on opening any media file, here's another log (no errors): |
Dockerfile:
Not having much luck here!
The text was updated successfully, but these errors were encountered: