The nettle patch for asdcplib looks for nettle installed in /usr
unless a path is specified. For cross builds, this either means
that it doesn't find the cross built nettle within the contribs
tree, or even worse, adds /usr/include to the include path in
the cross build.
tiff-4.0.7 keeps these files in a subdirectory named "config",
so the previous $(UPDATE_AUTOCONFIG) actually had no effect at
all.
This fixes building for non-x86 windows platforms.
The latest trunk version of clang (upcoming clang 6.0) has changed
the default to C++14, just like GCC 6.
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>
The rest of rules.mak assumes that either of them is set (and check
either "ifdef USE_FFMPEG" or "ifdef USE_LIBAV"), but by default
neither is set. If using the "ifndef USE_LIBAV" branch and fetching
sources from ffmpeg, make sure USE_FFMPEG is set in the rest of the
makefile.
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>
Checking for that specific symbol is not needed anymore since
the keychain lookup patch is not needed anymore. Additionally,
this patched a pkgconfig file which is not needed by vlc and is not
even installed / compiled.
Without this, when reconfiguring, BUILD_FILEVERSION will end up with
a trailing comma with no revision number, which means that
src/versioninfo.rc will have a syntax error on build.
To reproduce/understand, download the plain gcrypt tarball;
configure contains a line like this:
BUILD_FILEVERSION="${BUILD_FILEVERSION}45409"
After running configure, src/versioninfo.rc contains
"FILEVERSION 1,7,8,45409".
If running autoreconfigure with no enclosing git repo anywhere,
the same line in configure will end up as this:
BUILD_FILEVERSION="${BUILD_FILEVERSION}"
After configuring, src/versioninfo.rc will now contain
"FILEVERSION 1,7,8,", which results in syntax errors.
As long as an enclosing git repo is available somewhere (if
the surrounding vlc tree contains a .git directory), this isn't
an issue though.
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>
The previous version of win32.patch left things in a bit more broken state
than necessary.
The previous version of the patch removed LD=gcc and removed a number of
flags, making the build trying to build a DLL (but without the option
-shared), actually producing an EXE. (The linked DLLs are later
actually removed by the contribs build system.) Instead of removing LD=gcc,
change it into LD=$(CC) which is more what glew originally intended, and
keep the flags for linking shared libraries (but remove the -soname option
which isn't supported by neither GNU ld nor lld).
This fixes building in setups where $(LD) points to lld.
Signed-off-by: Hugo Beauzée-Luyssen <hugo@beauzee.fr>
When building the Qt tools for the target architecture in cross
compilation, the bootstrap object library is rebuilt. (In cross
builds of Qt, the tools are only built for the build host.
The VLC contribs build them manually for the targeted environment
afterwards.) The tools bootstrap library wasn't removed inbetween
though.
This meant that the object files for the second round (for the
cross target environment) were added to the bootstrap library for
the host environment. Most object files were just replaced, but some
few object files weren't built at all in cross builds for windows.
This meant that after cross-building the bootstrap library for windows,
it still contained a few object files for the native host build
environment as well.
lld-link errors out when it encounters object files in a static library
that it can't parse (in this case, ELF files when doing a windows cross
build).
Signed-off-by: Hugo Beauzée-Luyssen <hugo@beauzee.fr>
Clang errors out on casting from a pointer to a smaller integer
type.
This is an adapted backport of a newer upstream harfbuzz
commit 03b7a221f701a9b003890878e730ad175c3fdd86.
Signed-off-by: Hugo Beauzée-Luyssen <hugo@beauzee.fr>
Tristan Matthews
Martin Storsjö
Jean-Baptiste Kempf
Etienne Brateau
Steve Lhomme
Thomas Guillem
Jean-Baptiste Kempf
Hugo Beauzée-Luyssen
David Fuhrmann
Rémi Denis-Courmont
Marvin Scholz
Steve Lhomme