Thanks a lot Dave/Charlie. Let me test more, I could compile, but couldn't
make it work yet.

--Gopu


-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Dave Thompson
Sent: Friday, January 18, 2013 12:44 PM
To: [email protected]
Subject: RE: Windows 8 ARM: what is OPENSSL_Uplink_Table

>From: [email protected] On Behalf Of Gopakumar Pillai
>Sent: Friday, 18 January, 2013 14:36

>I had posted a mail about porting OpenSSL 0.9.8x to Windows 8 ARM 
>platform, haven't received any response.

>Let me ask another question.
>What is the purpose of OPENSSL_UplinkTable in ms\uplink.c? Since I am 
>not an assembly person, rewrote the initialization portion in C. Seems 
>like it's working for WIN32. Strange thing is that, even if I specify 
>an empty function to initialize, it works.
>That makes me wonder what is the pupose of this table and where is it
used.

It's to deal with the several incompatible C runtime libraries MS has on
Wintel, since an EXE and a DLL might use different libraries.

http://www.openssl.org/support/faq.html#PROG2 (read to end; the original
approach was just to prohibit differences)

It is used, dynamically, only when you pass FILE* opens across the EXE/DLL
interface, for example PEM_read_xyz but not PEM_read_bio_xyz with a
BIO_new_file fopen'ed in the DLL.

>Idea here is to make this code work for ARM too. I could compile/link 
>it, but the DLLs are not working.

I would hope that ARM/WinRT doesn't need this silliness and you can just
configure USE_APPLINK off. 


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to