-
Notifications
You must be signed in to change notification settings - Fork 54
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
Support for building aws-lc-rs with just rustc #152
Comments
This is potentially doable for the (non-fips) build of aws-lc, as that build doesn't require the use of the Go compiler. The challenge here would be specific to the static FIPS build, which is what requires the Go compiler. In particular the Go compiler is used to remove relocation entries from the FIPS module boundary of the resulting assembly code. This is done specifically by delocate, and more information can be found here. |
I think it's reasonable to focus on the non-fips build as an initial pass. For |
I concur. I've inherited aws-lc-rs through rustls, now I have to walk around 3 platforms we have and tell everyone how to install CMake which is sub-optimal and would rather avoid. |
My highest priority right now is eliminating the need for CMake when building for our primary platforms (Linux/MacOS on x86-64/aarch64). Progress is being made. You can watch this PR for the latest updates. |
As of release v1.7.0, CMake is no longer required to build aws-lc-rs for Linux/MacOS on x86-64/aarch64. For these platforms, only the minimal Rust & C toolchains should be required for the build to succeed. I'm going to close this issue now. Feel free to open another issue to request extending support for our no-cmake build to other platforms (e.g., Windows). |
Problem:
We'd love to include aws-lc-rs in the Rust SDK but feel that the current build requirements are too onerous for most customers to use it as the default.
Consider using
build.rs
to replaceCMake
to compileaws-lc-rs
. Perhaps we could also use the Rust compiler to achieve the static linking achieved with the Go compiler currently?The text was updated successfully, but these errors were encountered: