A direct dependent of this project should also use the x64 version of

openssl.gyp

Index: openssl.gyp
===================================================================
--- openssl.gyp	(revision 244037)
+++ openssl.gyp	(working copy)
@@ -21,6 +21,9 @@
           'openssl/crypto/modes',
           'openssl/include',
         ],
+        'openssl_public_include_dirs': [
+          'openssl/include',
+        ],
       },
       'sources': [
         '<@(openssl_common_sources)',
@@ -83,6 +86,7 @@
           'variables': {
             # Ensure the 64-bit opensslconf.h header is used.
             'openssl_include_dirs+': [ 'config/x64' ],
+            'openssl_public_include_dirs+': [ 'config/x64' ],

[Ryan Sleevi, 2014/02/05 02:13:03]

Is the public API affected by this (eg: including opensslconf.h)?

The way we've dealt with this in other third-party projects is to ensure the
#defines are included within the .gyp file, not the config.h file - or that the
config.h is only used internally when generating the library.

[wtc, 2014/02/05 17:14:32]

opensslconf.h is the only header under the config/x64 directory. (It's in an
"openssl" subdirectory.) So this change won't make other headers available to a
direct dependent.

opensslconf.h is a public header. (For example, on a Ubuntu Linux computer,
opensslconf.h is in /usr/include/openssl.) I don't think it is usually included
directly, but several public headers include it.

           },
         }],
         ['component == "shared_library"', {
@@ -107,7 +111,7 @@
       ],
       'direct_dependent_settings': {
         'include_dirs': [
-          'openssl/include',
+          '<@(openssl_public_include_dirs)',
         ],
       },
     },