we" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 18, 2004 12:26 PM
Subject: RE: Installation Trouble VC7 Win32
Oh yeah - that is the ticket! Thanks much for pointing me to iconsinc.com
Gray and Young have made that an easy process - only had to comment ou
Open a command line window and execute:
c:\program files\microsoft visual studio .net
2003\common7\tools\vsvars32.bat"
c:\program files\microsoft sdk\setenv.bat /2000 /RETAIL
prior to running NMAKE.
Chris Rowe wrote:
Thanks for your comments. It looks to me like the make file compiler
switche
Of Andrzej Posiadala
Sent: Wednesday, February 18, 2004 6:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Installation Trouble VC7 Win32
Hi Chris,
under this url
http://www.iconsinc.com/~agray/ossldev
you may find solution to your problem. It's a workspace for VC6 but works
fine for me with VC++
mailto:owner-[EMAIL PROTECTED]] On Behalf Of Steven Reddie
Sent: Tuesday, February 17, 2004
8:20 PM
To: [EMAIL PROTECTED]
Subject: RE: Installation Trouble
VC7 Win32
Sorry, spoke too soon. Not noticing
the scrollbar, my window size made the message look like it ended after the
"wheels
Hi Chris,
under this url
http://www.iconsinc.com/~agray/ossldev
you may find solution to your problem. It's a workspace for VC6 but works
fine for me with VC++ .NET 2003
Regards
Andrzej Posiadała
"Chris Rowe" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
2004-02-17 22:04
Please respond to o
Wednesday, 18 February 2004 10:06
AMTo: [EMAIL PROTECTED]Subject: RE: Installation
Trouble VC7 Win32
Elaborating on "wheels fall off" might make the problem easier to
diagnose. If X509_NAME is mentioned then it's probably a clash with the
Microsoft Platform SDK. With V
On Tue, Feb 17, 2004, Chris Rowe wrote:
> OK I am new to openssl and am experiencing difficulty building openssl. I
> have followed the install.w32 instructions to the letter, but still no luck
> on the nmake step.
>
> Does anyone have a makefile or project/solution file *.sln that simplifies
> t
Title: Message
Elaborating on "wheels fall off" might make the problem easier to
diagnose. If X509_NAME is mentioned then it's probably a clash with the
Microsoft Platform SDK. With VC6 the Platform SDK was a seperate optional
package and it was simply a matter of removing the Platform SDK
