Commit Graph

5 Commits

Author SHA1 Message Date
VZ 1a6f401773 Run the fuzzing script from the main wxWidgets repository (#3138)
This will make it simpler to extend and maintain the script, e.g. by
adding more fuzz targets.
2019-12-16 17:57:56 -08:00
jonathanmetzman 3049c50d48
Migrate projects using -lFuzzingEngine to $LIB_FUZZING_ENGINE (#2325)
Migrate from -lFuzzingEngine to $LIB_FUZZING_ENGINE where possible and not causing breakage
2019-05-01 11:09:55 -04:00
VZ 289dbbdf7c Build wxWidgets libraries statically (#915)
This ensures that the fuzzer can be ran from the output directory
without having to copy the shared libraries there too.
2017-10-24 18:19:29 -07:00
VZ 72e9d687ce Use CXXFLAGS also for linking when building wxWidgets (#914)
Otherwise the correct -stdlib=libc++ option, which is part of CXXFLAGS
defined in the Docker container, is not used resulting in link errors.
2017-10-25 11:53:45 +11:00
VZ ee358c11e4 Add wxWidgets project (#913)
Add the project file and simple Dockerfile and the build script using
the fuzzer source in the main wxWidgets repository itself.
2017-10-24 16:19:16 -07:00