You can build and link using banned API's , but when you run the app certification kit , it will give you a fail, and list of all the function calls you making that you can't make. If you use the .dll's , its even worse because it fail you for functions that your not using but because that dll is included it checks all functions.
So for the most part is was configuring w/ no sockets / no dgram , etc, since we just use mem bio's. The patches I'm putting together are in 2 flavors , stuff that doesn't compile cleany when that feature is turned off. And the other is the winrt/metro specific patch where it adds a new compile target and a couple of alternate implementations for functions that fail the certification tests. The areas that where using banned API's where some calls to windows event logger, catastrophic error, and random seed stuff. On Wed, Sep 19, 2012 at 5:17 PM, Andy Polyakov <[email protected]> wrote: >> For example, you *can* call MessageBox from Metro application if you >> declare it yourself and explicitly link with user32.lib. It makes lesser >> sense to do so, because you have to switch to desktop in order to interact >> with dialog, but it *is* possible. > > > Just to clarify. I'm not suggesting to keep using Win32 interface in WinRT > application. I'm only using this example to demonstrate that it's possible > to use "standard" OpenSSL build even in WinRT application context. So why > don't you? If something doesn't work or it's inappropriate to do so for some > reason, let's identify the problem, it might be possible to address it in > "standard" build. I mean there is more value in maintaining single source > suitable for multiple contexts than to split the effort. > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [email protected] > Automated List Manager [email protected] -- Charlie Lenahan ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
