Closed RSeroka closed 10 years ago
Hi, I had to disable a lot of features to be able to compile the library using the CrossBridge tool-chain:
no-asm no-ssl2 no-ssl3 no-dtls no-shared no-hw no-engines no-threads no-dso no-err no-npn no-psk no-srp no-gost no-ocsp no-sock
Thank you for quick response. It was very helpful to see how you built crypto
So put in some effort to build openssl-1.0.1j with config will lesser restriction set as shown below: no-asm no-ssl2 no-hw no-threads no-dso no-err no-npn no-psk no-srp no-gost
I produced a libssl.a! but the trouble I have now is much more basic than openssl. I can't link my application because _connect can not be found while linking.
Rather than change the topic of this thread, I'll post a new issue.
Thank you again.
Thank you for working on OpenSSL support.
I downloaded CrossBridge_15.0.0.3.zip from http://sourceforge.net/projects/crossbridge-community/files/15.0.0/ and found that the libssl.a is missing from the sdk/usr/lib directory
$ find /cygdrive/c/Applications/Crossbridge/15.0.0.3/sdk/ -name libssl* /cygdrive/c/Applications/Crossbridge/15.0.0.3/sdk/usr/lib/pkgconfig/libssl.pc
$ find /cygdrive/c/Applications/Crossbridge/15.0.0.3/sdk/ -name libcrypto* /cygdrive/c/Applications/Crossbridge/15.0.0.3/sdk/usr/lib/libcrypto.a /cygdrive/c/Applications/Crossbridge/15.0.0.3/sdk/usr/lib/pkgconfig/libcrypto.pc