-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eliminating build dependency on Go #13
Comments
I would absolutely be interested in this! I'm particularly interested in (2) and (3), as I expect I should be able to pre-generate Also, if you're interested in taking this one step further (not necessarily now, but at some point in the future), I've been hoping to eliminate the need for the two-phase build entirely by updating the |
IIUC, we'll still need (1) in order to fully remove the dependency on Go, even if we remove CMake and drive the compilation manually from the build script. @davidben, correct me if I'm wrong on that? |
You can use the branch "master-with-bazel" or "chromium-stable-with-bazel" maintained by boringssl team to get rid of go. |
Currently, building Mundane requires Go 1.11+. Utilities in Go are used for three tasks:
Generating the interned error message bundle and its index (
crypto/err_data.c
in the build tree, fromcrypto/err/*.errordata
in the source tree).Extracting the names of public symbols from the archive created in the first library build (
crypto/libcrypto.a
) and saving the result insymbols.txt
above the two build directories.Generating the headers with substitutions from regular to versioned symbol names, using the result of the previous utility.
Those are rather simple programs and I have reimplemented them in Rust without much difficulty. Integrating them into
build.rs
could lead to elimination of Go as a build dependency of Mundane. While having any single dependency is not particularly onerous, I believe that minimizing their number eases the acceptance of a package, both for developers and end users. Even more so since Go 1.11 is not available on current LTS versions of popular distros.Would there be any interest of pursuing this further?
The text was updated successfully, but these errors were encountered: