> IF EXIST libcrypto-1_1-x64.dll.manifest DEL /F /Q > libcrypto-1_1-x64.dll.manifest > link /nologo /debug /dll /implib:libcrypto.lib > /out:libcrypto-1_1-x64.dll /def:libcrypto-1_1-x64.def > @C:\Users\jesaremi\AppData\Local\Temp\nm8557.tmp || (DEL /Q libcrypto.* > libcrypto-1_1-x64.* && EXIT 1) > crypto\aes\aes_cfb.obj : fatal error LNK1112: module machine type 'X86' > conflicts with target machine type 'x64' > NMAKE : fatal error U1077: 'link' : return code '0x1' > Stop. >
It sounds like the wrong Developer Tools Command Prompt was opened. You can find them through Start -> Programs -> Visual Studio NNNN -> Developer Tools. Also see https://msdn.microsoft.com/en-us/library/ms229859(v=vs.110).aspx . If you plan on building for x86 and you configure for VC-WIN32, then be sure you open the x86 command prompt, and not the x64 one. If you want to build for x64, then be sure to configure with VC-WIN64A, and be sure to open a x64 developer command prompt. If you have the correct command prompt open, then perform a clean or distclean. You may have old artifacts lying around. Jeff
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users