This is a discussion on Re: Visual Studio 2005 and openssl question - Openssl ; Ok finally got it to run in standalone. Using an XP machine that does not have VC2005 installed best is the: \Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bootstrapper\Packages\vcredist_x86\vcre dist_x86.exe and run that for 2000 machines you will need the Windows Installer 3.0. ...
Ok finally got it to run in standalone. Using an XP
machine that does not have VC2005 installed best is
\Program Files\Microsoft Visual Studio
and run that for 2000 machines you will need the
Windows Installer 3.0.
In addition I did what Brad said with the manifest
files and .exe,.dll and putting them side-by-side and
everything worked like a charm. Thanks again Brad.
I can now sleep.
--- gary clark
> Much appreciated Brad. Is this documented anywhere?
> I totally agree that this stuff has nothing to do
> openssl-dev. I wasnt receiving the right information
> that helped me solve the problem in openssl-users.
> information you have given should be documented at
> least on the FAQ. I was at a loss on what I was
> and sometimes the little things I missed count alot.
> Pushing the dll to the same directory as the
> application and the caveats? Huh! I would think that
> dlls should reside in system32?
> Anyway much appreciated and I hope this is now
> --- Brad House
> > > Well that didnt fly either. Has anybody built an
> > > openssl app using VS2005 and ported it to a XP
> > machine
> > > that does not have openssl installed? If they be
> > so
> > > kind and shed some light onto this dark area
> > > would be appreciated because I thought this
> > be
> > > easy which it is providing you do complete
> > of
> > > openssl.=20
> > >=20
> > > If you try to build the static libs all is OK
> > except
> > > you will get conflicts with VS2005 and there
> > the
> > > problem of using the /MD in the code generation
> > which
> > > I'm led to believe from the FAQ I have to do.
> > >=20
> > > The instructions do not seem to be clear when
> > building
> > > for VS2005.
> > I'm not sure why you think this is a VS2005 issue.
> > We've
> > been deploying apps which depend on the OpenSSL
> > libraries
> > built with VS2005 for the last year or so (prior
> > that,
> > we used VS2003). There's really not much to it.=20
> > Make
> > sure you copy these files:
> > libeay32.dll
> > libeay32.dll.manifest
> > ssleay32.dll
> > ssleay32.dll.manifest
> > to the _same_ directory as your application runs
> > from, I
> > wouldn't recommend trying to put them in your
> > directory.
> > That is the primary search path for all DLLs on
> > windows
> > and is strongly recommended that you deploy
> > in that manner to prevent conflicts with other
> > applications
> > which may link to other versions of openssl.
> > Yes, those manifest files are something new with
> > VS2005.
> > Also make sure you deploy the manifest files for
> > your
> > MSVC runtime, along with MFC or whatever else you
> > may
> > be using. What error are you seeing that make you
> > think
> > this would be anything related to OpenSSL to begin
> > with?
> > Please use the openssl-users list for this kind of
> > stuff
> > though. This has nothing to do with openssl-dev
> > -Brad
> > OpenSSL Project =20
> > http://www.openssl.org
> > Development Mailing List =20
> > email@example.com
> > Automated List Manager =20
> > firstname.lastname@example.org
> OpenSSL Project =20
> Development Mailing List =20
> Automated List Manager =20
OpenSSL Project http://www.openssl.org
Development Mailing List email@example.com
Automated List Manager firstname.lastname@example.org