* libass: update contact list
One contact is retired; another is currently inactive.
* libass: don't build HarfBuzz tests
They won't be used, so this just wastes resources.
* libass: upgrade to Ubuntu 20.04
The build failures on 20.04 were due to explicit listing
of static library dependencies, which have changed on 20.04:
png12 was replaced by png16, fontconfig was missing -luuid,
and png needed -lz to follow it, not precede.
Replace the explicit -l list by $(pkg-config --static --libs).
However, -lm must be filtered out as it causes linker errors:
> undefined reference to `_dl_x86_cpu_features'
While we are at it, Ubuntu 20.04 comes with new-enough FriBidi,
so we can stop building it.
It also has new-enough HarfBuzz, but it depends on libgraphite2,
which lacks a static library in the system package, and dynamically
linking against a system library does not work in OSS-Fuzz
as the shared object will not exist in the run-time environment.
Reorder the dependencies alphabetically for consistency.
* varnish: Drop the downstream build system patch
I made sure future changes upstream would less likely break OSS-Fuzz
builds by adding an explicit --enable-oss-fuzz configure option.
* varnish: Reduce build parallelism
The partial build performed seems to be subject to races with 32 CPUs.
* varnish: This is a C project, not C++
Not sure how much this matters, it may change environment variables set
during the build with for example CFLAGS instead of CXXFLAGS. Or it
might just be for statistics reasons? Anyway, this is a C project.
Now that the CMake files for int have been fixed, so that when
LIB_FUZZING_ENGINE is set, it is used as the sole way of specifying
fuzzer-related linker flags, the honggfuzz engine should work. This
change reverts the project to use the default set of fuzzing engines,
which includes honggfuzz.
The LIB_FUZZING_ENGINE environment variable is now passed to tint's
CMake command as an option, rather than having the environment variable
be queried in the project's CMake files.
Now that the CMake files for spirv-tools have been fixed, so that when
LIB_FUZZING_ENGINE is set, it is used as the sole way of specifying
fuzzer-related linker flags, the honggfuzz engine should work. This
change reverts the project to use the default set of fuzzing engines,
which includes honggfuzz.
Now that the CMake files for spirv-tools have been fixed, so that when
LIB_FUZZING_ENGINE is set, it is used as the sole way of specifying
fuzzer-related linker flags, the honggfuzz engine should work. This
change reverts the project to use the default set of fuzzing engines,
which includes honggfuzz.
The LIB_FUZZING_ENGINE environment variable is now passed to the CMake
command of spirv-tools as an option, rather than having the environment
variable be queried in the project's CMake files.
* Helper flags for swift compilation
* Documentation for swift project integration
* Adds swift to the languages with coverage
* Only thread sanitizer is supported
* Fixes swift coverage target compilation
* fixup flags facotring
* swift: run on new ubuntu
* fixup
* swift: right copy for symbolizer
Currently there are errors building with honggfuzz. This may be because
the tint fuzz targets are not correctly configured - the tint build
system does not use the LIB_FUZZING_ENGINE environment variable and
instead hard codes various fuzzer flags. This will be fixed in due
course, but disabling honggfuzz for now to get the OSS-Fuzz build
working.
Guido Vranken