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

libssl.a libcrypto.a #3254

Open
Raimo33 opened this issue Jan 31, 2025 · 4 comments
Open

libssl.a libcrypto.a #3254

Raimo33 opened this issue Jan 31, 2025 · 4 comments
Assignees

Comments

@Raimo33
Copy link

Raimo33 commented Jan 31, 2025

Why only dynamic libraries? I need static linking for maximum performance

@Raimo33
Copy link
Author

Raimo33 commented Jan 31, 2025

root@pc/build # ls /usr/lib64/libssl.a /usr/lib64/libcrypto.a
ls: cannot access '/usr/lib64/libssl.a': No such file or directory
ls: cannot access '/usr/lib64/libcrypto.a': No such file or directory

@ephut ephut removed the new label Feb 13, 2025
@ephut
Copy link

ephut commented Feb 13, 2025

Given that wolfSSL was added, is this still needed?

@Raimo33
Copy link
Author

Raimo33 commented Feb 13, 2025

Not for my project right now. Plus apparently it's not possible to link openssl statically as it still needs access to dynamic libraries at runtime.

But generally I would appreciate it if you included the statically compiled libraries as well in your devpkgs

@fenrus75
Copy link
Contributor

fenrus75 commented Feb 13, 2025 via email

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

4 participants