-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
test: Add a fully static build with A/V support. #258
Conversation
2be25dc
to
b288098
Compare
Does the a/v and x11 integration actually work through a Docker image? What arguments you pass when running the container to make them work? When I was making the static tarball (not a Docker container) build of toxic I had to disable a/v for some reason. I think OpenAL-Soft was detecting which audio libraries I have at build-time, enabling only the audio backends for those libraries (well, afterall it can't built other backends with missing headers and library symbols), and then also hardcoding paths to their so-names to |
Hm, I see |
b288098
to
59f0215
Compare
I don't know if it works in docker. Probably you can volume-mount enough X11 stuff into it to make it work. I only tested that it works in the terminal and that it connects. I don't have a working X server to test with at the moment. |
aff6242
to
055e040
Compare
055e040
to
8bc2283
Compare
Closing for inactivity and pushback. |
Eh? What pushback? If you have interpreted my comments as a pushback then you are very mistaken, this PR is welcome by me. I have only expressed my surprise at you getting this to work and me not knowing of the |
I tested it and the A/V didn't work. I'm not against it though, I think it'd be great to get it working and merged. |
This change is