Problem in Building openssl_1.0.2p in Visual Studio 2015

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem in Building openssl_1.0.2p in Visual Studio 2015

Swamy J-S

Am building new release of openssl_1.0.2p using Visual Studio 2015 Command Prompts. I have installed perl and sed. I have written some batch files to build x86 and x64 libraries. When I built same openssl version in VS 2013 and VS 2017 am not facing any issue.

 

But while building in VS 2015 am unable to build. When I build x86 library in “VS2015 x86 Native Tools Command Prompt” then  its building fine and resulting in generating include and lib folder. But when I try to build DLL library then am getting fatal error which says

 

rc /fo"tmp32dll\libeay32.res" /d CRYPTO ms\version32.rc

 

‘rc’ is not recognized as an internal or external command,

operable program or batch file.

 

NMAKE : fatal error V1077: ‘rc’ : return code ‘0x1’

Stop.

        1 dir(s) moved.

        1 dir(s) moved.”

 

I have attached screenshot too.

 

Thanks and Regards,

SWAMY J S

 


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

VS 2015.png (82K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Problem in Building openssl_1.0.2p in Visual Studio 2015

Michael Wojcik
> From: openssl-users [mailto:[hidden email]] On Behalf Of Swamy J-S
> Sent: Thursday, August 30, 2018 08:04

> But while building in VS 2015 am unable to build. When I build x86 library in “VS2015 x86 Native Tools Command
> Prompt” then  its building fine and resulting in generating include and lib folder. But when I try to build DLL library
> then am getting fatal error which says

>  ‘rc’ is not recognized as an internal or external command,
> operable program or batch file.

This is a Visual Studio issue, not an OpenSSL one. You should really be asking on a Visual Studio forum.

rc is part of the Visual Studio toolchain, so the problem is either in your Visual Studio installation or your environment. The latter is more likely.

The problem may be that you're using an x86 Native Tools window. If you're running on a 64-bit version of Windows, you should be using a Visual Studio x64 x86 Cross Tools window.

--
Michael Wojcik
Distinguished Engineer, Micro Focus


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users