Last active
September 24, 2021 04:57
-
-
Save danielbene/99b922641d1ff55e9cf1f00435f07323 to your computer and use it in GitHub Desktop.
VLC 3.x cross-compilation steps in 2020 Q4
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I had to build VLC 3.x from src, and the below steps was the only way that I could achieve this in late 2020. | |
After many hours, I faced the problem that most of the tutorials out there are so outdated that they just cant work nowdays. | |
I builded it for Windows x64, on a Pop_os 20.04 VM using a builder container. | |
I don't know if it works with dev or not, and I can't even trust it to work after like half year, but here it is. | |
Tip: check build.sh manual for options. | |
BUILD STEPS: | |
1. install docker (https://gist.github.com/danielbene/98d7a5b08fd5c2c18d4883f250e4b6c6) | |
2. cd ~ | |
3. mkdir win64 | |
4. sudo docker run -v ~/win64:/win64 --name builder -i -t registry.videolan.org:5000/vlc-debian-win64 /bin/bash | |
5. apt-get update && apt-get install python -y | |
6. cd win64 | |
7. git clone https://code.videolan.org/videolan/vlc-3.0.git | |
8. cd vlc-3.0 (edit src here if needed) | |
9. ./extras/package/win32/build.sh -a x86_64 (first build takes 1+ hour) | |
10. cd win64 | |
11. make package-win32-zip (creates a portable zip package - very nice) | |
RE-RUN (after reboot or something): | |
1. sudo docker start builder | |
2. sudo docker exec -i -t builder /bin/bash | |
3. ./extras/package/win32/build.sh -a x86_64 && cd win64 && make package-win32-zip && cd .. && echo -----FINISHED----- | |
- after the first build, it only compiles changed files, so it takes like 5 minutes | |
- for stopping the builder container: sudo docker stop builder | |
- check if its running: sudo docker ps --all | |
src: https://forum.videolan.org/viewtopic.php?t=146175 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment