I had a chance to take abother look and the offending target is actually ppGoogleNaClPluginChrome. I've attached the build log I get running: ninja -vC out\Debug_x64 ppGoogleNaClPluginChrome

My only guess here is that we're passing the wrong lib type (ia32 vs. x64) or something along those lines in one of the build files.

fail_log.txt 20.7 KB View Download

Randomly adding @bbudge from the pepper team since this seems to be specific to the NaCl plugin.

Justin actually intended to build with:

GYP_DEFINES=target_arch=x64

building with GYP_DEFINES=component=shared_library actually works fine.

I can't reproduce the issue with either a shared or static library build. I could be missing something though...

Okay, my guess is that I'm the only one with a src-internal checkout, meaning I have platform SDK files under third-party. Since you don't have those directories present, your x64 build doesn't get its dependencies squashed by the ia32 AdditionalLibraryDirectories in native_client/build/common.gypi. If I remove those AdditionalLibraryDirectories entries, my build gets past the linking errors.

So, can I just remove those entries from common.gypi and rely on config.gypi to pick up the right ones for a NaCl standalone build? Because Chrome's common.gypi does the right architecture switch (if the settings don't get squashed).

NaCl rolled forward and this is fixed. Only one build error left in NaCl for all targets.