| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This define was always just a stopgap for that two month period (August
2021 - October 2021) where the bytes_read field in ffmpeg was completely
missing. Before that time, it was a private member in a struct (which
mpv used). Afterwards, it officially became public. Fortunately, the
lack of this field never actually made it into a release, so it could
have only possibly affected people building from the master branch.
Since ffmpeg 5.0 came out recently, and it's been plenty of months since
that two month window, we can go ahead and drop this check. This
finishes up the work done in 78cfeee2b93830f2988508a653b508336147b79d.
Sidenote: the cached ffmpeg version in the mingw ci were from that time
period when the bytes_read field was missing. The N in the workflow is
bumped to force a full rebuild and fresh clone of ffmpeg.
|
| |
|
|
| |
We have this ao again since #9298 so let's run it through the CI.
|
| |
|
|
|
|
|
|
|
| |
When this was originally added, some OS package managers were slow and
behind the required meson version needed for mpv to build. Both opensuse
tumbleweed and freebsd now appear to carry meson 0.60.3 in their repos
so we no longer need to do the two-step process of installing pip3 and
then installing meson via pip. Instead, just use the OS package manager
version.
|
| |
|
|
|
| |
The old directory was wrong. The actual build directory has the matrix
prefix in its name.
|
| |
|
|
|
|
|
|
| |
Update the github workflows to also do meson builds for every OS.
Additionally, make every workflow execute the built mpv executable
(except for windows and FreeBSD's waf executable) to make sure that it
runs. As an aside, FreeBSD unfortunately is a bit less elegant since it
is in a VM.
|
| |
|
|
|
|
|
|
| |
I find it both hilarious and sad that Github decided that defaulting
to XCode 13.0 was a good idea... At least they added 13.1 quickly.
Ref actions/virtual-environments#4180
Ref actions/virtual-environments#4300
|
| | |
|
| |
|
|
| |
This image has finally become public.
|
| |
|
|
|
|
|
|
|
|
| |
This CI builder bases on openSUSE Tumbleweed, and recently had
its glibc updated. This led to new syscalls such as 'clone3' not
being allowed through the security layer.
Can be reverted after Github Actions updates their security policy.
actions/virtual-environments#3812
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Requested to be changed while at it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
this creates a default log for the last mpv run when started from the
bundle. that way one can get a log of what happened even after an issue
occurred. also add a menu entry under Help to show the current log, but
only when the bundle is used.
Fixes #7396
Fixes #2547
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
It's not that we _want_ the log to be on an external site. We just want
the log, somehow. Probably not pasted inline into the issue text.
Also reword the "we are assholes who really want logs" part of the text.
It's a subtle balance between trying to be nice and being a complete
asshole, but no matter what you do, it will always sound like the
latter, so be direct.
|
| |
|
|
|
| |
--log-file uses debug log level by default. On command line, -v -v will
use debug log level.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
How hard can it be? I know contribute.md is a shitty wall of text, but
that doesn't make it less important, and each violation will make it
take longer by adding another review round anyway.
And we really don't need lazy pull requests. If you can't be assed to
follow a few simple rules, your code is probably shit or you wanted to
be quick and lazy. Why should we accept it? We're the ones who have to
maintain it and fix bugs in it, and if the contributor is lazy, the
chance of you maintaining it is probably slim as well. On the other
hand, WE the maintainers are not obligated to anything.
Don't say that though, the first contact doesn't need to be negative. I
don't know if the "lazy pull requests" is still too strong, but I can't
tell.
|
| |
|
|
|
|
| |
Most files are LGPL anyway by now. contribute.md still requires
contributors to provide changes under LGPL, which should cover changes
to files that are LGPL, as well as GPL files.
|
| |
|
|
| |
The latter seems to give 500 errors more often than not these days.
|
| |
|
|
| |
Is there even anything that fucking sucks more than it?
|
| |
|
|
| |
Since some users apparently can't figure this out.
|
| |
|
|
|
|
| |
I guess there is a hard to balance tradeoff between appearing rude or
dismissive, and making the user think it's ok to not provide essential
information.
|
| | |
|
| | |
|
| |
|
|
|
| |
Word this sentence slightly more positively because we are a positive
project.
|
| |
|
|
|
| |
Also, try to save users from trying to use the github file upload
function. While we're at it, also make the sprunge.us hint a link.
|
| | |
|
| | |
|
|
|
I do not understand why github requires adding this crap to source code
repositories themselves, instead of making them part of the repository
configuration. Remove CONTRIBUTING.md to compensate for github crap
accumulating.
|
