Skip to content
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

incorrect feature probes for CMake add_subdirectory builds #4843

Open
jmayclin opened this issue Oct 14, 2024 · 0 comments
Open

incorrect feature probes for CMake add_subdirectory builds #4843

jmayclin opened this issue Oct 14, 2024 · 0 comments

Comments

@jmayclin
Copy link
Contributor

Problem:

The s2n-tls Cmake build includes support for an "in-source" build. Context for this support can be found in #2714 which added the functionality.

Using this in-source build will disable several important features, because s2n-tls feature probes (try-compiles) are not correctly executed when using the "in-source" build.

Solution:

Unknown.

Option 1: Remove Support For In Source Build

  • add documentation explicitly warning against using add_subdirectory with s2n-tls.
  • remove all in-source build functionality

Option 2: Document Limitation

For customers that always build with the same libcrypto, they might prefer a workaround that just reuses statically known libcrypto capabilities.

For example.

  1. a customer runs the feature_probes out of band to generate a configuration file
  2. a customer checks in the configuration file
  3. a customer uses the in-source build with the configuration file. No try-compiles are executed, but features are still correctly configured
  4. a customer continuously runs the feature_probes out of band (e.g. in ci) to assert on the correctness of the configuration file.

I haven't thought deeply about what s2n-tls would need to provide to enable this, but a good starting point would be documentation and a working example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants