-
-
Notifications
You must be signed in to change notification settings - Fork 335
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
opensslconf.h is correct for one architecture; and not the others #23
Comments
|
It's done now. |
krzyzanowskim
added a commit
that referenced
this issue
Apr 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
opensslconf.h
is generated anew for each configuration of OpenSSL. Its _not_ safe to use oneopensslconf.h
for all OpenSSL configurations. Also see Is it safe to build the cURL library as multi-arch? (same problem, different library).From the looks of
opensslconf.h
located in include-ios/openssl, it appears the conf file is for i386 (i.e., iOS debugging):The work around for fat binaries is to copy each
opensslconf.h
with a new name. I.e, theopensslconf.h
generated witharmv7
would be namedopensslconf-armv7.h
, theopensslconf.h
generated withi386
would be namedopensslconf-i386.h
, and so on.Then, you provide one
opensslconf.h
which gathers up the architecture dependent conf files:My apologies if I am parsing things incorrectly.
The text was updated successfully, but these errors were encountered: