title: Trouble with libcrypto/OpenSSL in Mac App Store application
body: <p>I'm preparing my application for the Mac App Store and as part of that, I've dropped in Nick Paulson's NPReceiptVerification and have been trying to get things working. It's a pretty simple setup, but from what I gather you're supposed to compile libcrypto into your application as a static library to avoid compromise by way of changing out dynamic libraries.</p>
  
  <p>This means that I need to provide my own libcrypto.a (if I understand correctly). I've compiled it myself and added it to my Xcode project. The problem now is that for some reason, when compiling my project Xcode just outright ignores the libcrypto in the project and instead jumps for a dylib version elsewhere on the system which lacks a 64-bit binary and thus causes the compile to fail.</p>
  
  <p>What can I do to make Xcode use the compiled version of the library? I know this might seem like a simple thing, but as a hobbyist Cocoa programmer who's only worked with Apple's libraries this all seems alien.</p>
  
  <p>Thank you!</p>