Commit Graph

59 Commits

Author SHA1 Message Date
Balachandar Namasivayam 479dbf4c04 Addressed review comments.
Remove redundant FDBLibTLS/ITLSPlugin.h.
2018-05-09 16:16:09 -07:00
Balachandar Namasivayam 788e6acb32 Add FDBLibTLSVerify files to build system. 2018-05-08 16:45:57 -07:00
Balachandar Namasivayam f71e13fa4d TLS Plugin Changes. 2018-05-08 16:27:21 -07:00
Alvin Moore 05c1a887f2 Changed the name of the TLS artifact to fdb-libressl-plugin.so 2018-05-07 16:47:46 -07:00
Alec Grieser 55e0b2f399
change file name within comment to be, like, the correct name 2018-04-19 10:19:50 -07:00
Alec Grieser fced3c61b3
fix headers of FDBLibTLS files 2018-04-19 10:11:55 -07:00
Alex Miller 5efd9fe3c4 Integrate FDBLibTLS into the FoundationDB build system.
This includes...
 * A minimal vcxproj file to list all the source files required for the build.
   Some future Visual Studio user can come along and replace it with a real
   actual vcxproj file with all the other metadata that I didn't bother to copy.
 * A local.mk file to specify all the custom flags and libraries we need for
   the build/link of the TLS plugin.
 * Including the project in the list of all FDB sub-projects
 * Fixes `make clean` to wipe all of lib/, including libFDBLibTLS.so

And offers a target of `bin/FDBLibTLS.so` that can be built, and I have
verified that it works with simulation.

Note that this requires a build image that contains the previous Dockerfile changes.
2018-04-12 14:13:02 -07:00
Alex Miller 5c65584aac Explicitly export `get_plugin` from FDBLibTLS Plugin.
For some reason, on some platforms it ends up as a local symbol, even though we
point the linker at the symbol map to expose it.  Double-requesting its
exportation makes it appear, though there's possibly a better solution.
2018-04-12 14:13:02 -07:00
Alex Miller 53e8a84bef Import LibreSSL TLS Plugin.
This does not integrate it into the FoundationDB build system at all, though
the original Makefile exists and could be used to build this plugin.
2018-04-12 14:13:02 -07:00