Re: Build problems on Windows

[jeff saremi <jeffsaremi@xxxxxxxxxxx>]

thanks a lot. I opened a "VS2015 x64 Native Tools" window as opposed to a "VS2015 x64 x86 Cross Tools" and everything worked amazingly with no issues.

The names are super confusing.

but i'm ok now. thanks

---

From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> on behalf of Jeffrey Walton <noloader@xxxxxxxxx>
Sent: Tuesday, January 10, 2017 11:52 AM
To: OpenSSL Users
Subject: Re: Build problems on Windows

 

        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 .

Developer Command Prompt for Visual Studio

msdn.microsoft.com

The Developer Command Prompt for Visual Studio automatically sets the environment variables that enable you to easily use .NET Framework tools.

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