With autoconf 2.70, the following warnings are emitted:
configure.ac:56: warning: AC_PROG_LEX without either yywrap or noyywrap is obsolete
./lib/autoconf/programs.m4:716: _AC_PROG_LEX is expanded from...
./lib/autoconf/programs.m4:709: AC_PROG_LEX is expanded from...
configure.ac:56: the top level
The documentation[1] of autoconf now states:
> Prior to Autoconf 2.70, AC_PROG_LEX did not take any arguments, and
> its behavior was different from either of the above possibilities: it
> would search for a library that defines yywrap, and would set LEXLIB
> to that library if it finds one. However, if a library that defines
> this function could not be found, LEXLIB would be left empty and LEX
> would not be reset. This behavior was due to a bug, but several
> packages came to depend on it, so AC_PROG_LEX still does this if
> neither the yywrap nor the noyywrap option is given.
>
> Usage of AC_PROG_LEX without choosing one of the yywrap or noyywrap
> options is deprecated. It is usually better to use noyywrap and define
> the yywrap function yourself, as this almost always renders the LEXLIB
> unnecessary.
The behaviour of the argument on autoconf < 2.70 is to ignore the
argument, so there are no issues with adding the option.
[1] https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.70/html_node/Particular-Programs.html#Particular-Programs
(cherry picked from commit 824b3d4551)
Signed-off-by: Marvin Scholz <epirat07@gmail.com>
Use the existing pkg-config file to detect presence of libgme. This file
is already shipped on all known libgme versions (checked back until
0.6.0, which is from 2015).
This fixes build with recent libgme versions, which added even more
dependencies which were missing in the old check.
Fixes#27262
(cherry picked from commit 3a08825c8a)
This was added ostensibly to fix compilation of the run-time AltiVec
test which was removed in bc146294cf.
Unfortunately, it causes the compiler to emit AltiVec instructions,
such that the executable crashes if AltiVec is not available.
Regression from e48d619555.
(cherry picked from commit 4af9c85184)
Recent commits use defines like SRT_LIVE_DEF_PLSIZE, which are
only available starting with that srt version.
(cherry picked from commit 80b149ddf9) (edited)
edited:
* 3.0 was restricting to < 1.3.0
Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
After 9e7ed0247d the test for the environment
variable wasn't done properly. Resulting in empty variables (and error messages
during configure).
Fixes#26165
(cherry picked from commit 0357c443e2) (rebased)
rebased:
- the 3.0 branch doesn't have [] around the variable names
Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
This allows passing a specific value instead of inheriting these
values from the build environment.
Fixes#26035
(cherry picked from commit 9e7ed0247d) (edited)
edited:
- the 3.0 branch doesn't have [] around the variable names
Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
When the macOS notifications module was disabled due to lack of Growl
framework in contribs, this was not properly checked for in the package
Makefile, resulting in a failure due to the missing framework.
This is a lot more accurate and wastes a lot less time than the Query approach.
The D3D11 Fence value is set when the GPU is done doing the previous
(rendering) commands. Then we can wait in the CPU for this event and return when
it's done. All decoder/filter commands seem to not have any impact so that's
really the signal we're looking for to tell the core we're done rendering.
This is only supported on newer mingw toolchains and only on Windows 10
Creators Update, which should cover pretty much all Win10 installed machines.
Better fixes#21600
(cherry picked from commit 61dbb36ebd) (edited)
edited:
- the release of resources is done in a more flat function
- this branch didn't use pointers for d3dev
Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
On Windows on ARM/ARM64, OpenGL isn't available. (For emulation
of i386 binaries, there is an opengl32.dll, but it's only the
fallback software renderer, nothing else. For ARM and ARM64, there
is no opengl32.dll.)
(cherry picked from commit 0d0aef05c1)
It may link with iphlpapi but be forbidden in UWP.
This test relies on the fact that -Werror-implicit-function-declaration works
in the compiler. And that's why it's done after it's enabled.
It's only used for the --miface option to set the preferred multicast interface.
(cherry picked from commit 424e8991d3) (edited)
edited:
- if_nametoindex was already detected, so just moved the code after the
-Werror-implicit-function-declaration test
Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
This will only be enabled when building windows targets and will only work when
compiling with Clang.
(cherry picked from commit cb3e3498d8) (rebased)
rebased:
- the code around the added AM_CONDITIONAL is different in this branch
Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
Compiling with Xcode 11 automatically enables the -fstack-check feature
which causes stack checking error due to unaligned stack which seem
to not be true. Lots of projects are affected by this currently
so hopefully this will be fixed in an Xcode update.
(cherry picked from commit 856ddd8d1a)
Signed-off-by: Marvin Scholz <epirat07@gmail.com>
The default value of _WIN32_WINNT isn't something that is built into
the compiler, but is defined by the toolchain headers.
Include windows.h after including ws2tcpip.h/winsock2.h, since those
headers should be included in that particular order.
(cherry picked from commit 22fed9624f)
If the toolchain defaults to a newer version of windows, this
function is available there, but the previous configure checks
didn't notice it. Force testing with both compiling and linking,
as the function exists in import libraries, but only is visible
in headers since Vista.
On the master branch, the function was taken into use
unconditionally in c0bf5aeefc.
Since 255e2ce27, we try not to override _WIN32_WINNT in case it already
is defined on the command line to a higher value. However, if it isn't
specified on the command line, but the toolchain headers default to
a newer version, we should also honor it and keep that version instead
of forcing a lower version here. (If the toolchain defaults to a newer
version, runtime libs of the toolchain may rely on such a new version
anyway, so forcing a lower target within VLC might be useless.)
EDIT: Adapted to a different default version in the 3.0 branch.
(cherry picked from commit 0d65fe038a)
Definitions from AH_TOP aren't included in the configure checks.
This was the original intent of e807c8e91.
This makes sure configure checks and actual compilation are run
with the same version defined.
EDIT: Adapted to a different default version in the 3.0 branch.
(cherry picked from commit 0a27328b5a)
Jean-Baptiste Kempf