Quote: 2. Installation ------------------------------------------------------------------------------- The usual configure [--disable-static] [--enable-debug] make make check make install should do the trick. You can skip the "make check" parts if you do not want to run the regression tests.To be more specific, I've noticed libraries usually ship with a file called CONFIGURE, another called MAKEFILE, and perhaps another called INSTALL. The extensions are usually missing, but sometimes they include .in, .bat, .bak, and various others. Since most docs lack the explanation for what to do with these, can someone provide a quick one for me? --- And here's a much more specific case. I'm trying to install the OpenSSL library. Here are the instructions for installing on Win32 using Visual C++:
Quote: Visual C++ ---------- If you want to compile in the assembly language routines with Visual C++ then you will need an assembler. This is worth doing because it will result in faster code: for example it will typically result in a 2 times speedup in the RSA routines. Currently the following assemblers are supported: * Microsoft MASM (aka "ml") * Free Netwide Assembler NASM. MASM is distributed with most versions of VC++. For the versions where it is not included in VC++, it is also distributed with some Microsoft DDKs, for example the Windows NT 4.0 DDK and the Windows 98 DDK. If you do not have either of these DDKs then you can just download the binaries for the Windows 98 DDK and extract and rename the two files XXXXXml.exe and XXXXXml.err, to ml.exe and ml.err and install somewhere on your PATH. Both DDKs can be downloaded from the Microsoft developers site www.msdn.com. NASM is freely available. Version 0.98 was used during testing: other versions may also work. It is available from many places, see for example: http://www.kernel.org/pub/software/devel/nasm/binaries/win32/ The NASM binary nasmw.exe needs to be installed anywhere on your PATH. Firstly you should run Configure: > perl Configure VC-WIN32 --prefix=c:/some/openssl/dir Where the prefix argument specifies where OpenSSL will be installed to. Next you need to build the Makefiles and optionally the assembly language files: - If you are using MASM then run: > ms\do_masm - If you are using NASM then run: > ms\do_nasm - If you don't want to use the assembly language files at all then run: > ms\do_ms If you get errors about things not having numbers assigned then check the troubleshooting section: you probably won't be able to compile it as it stands. Then from the VC++ environment at a prompt do: > nmake -f ms\ntdll.mak If all is well it should compile and you will have some DLLs and executables in out32dll. If you want to try the tests then do: > nmake -f ms\ntdll.mak test To install OpenSSL to the specified location do: > nmake -f ms\ntdll.mak installI've followed those instructions blindly up to a point. I'm a bit lost with this step: Then from the VC++ environment at a prompt do: > nmake -f ms\ntdll.mak So, where do I run this command? In Visual Studio, I am aware that there is a window called the "command window", which looks a lot like a command prompt. But there is no such instruction there as "nmake". It's an unrecognized command. Neither did I find any mention of "nmake" in the directory where I installed the library (I searched the directory, but it turned up nothing). So it is neither a command recognized by Visual Studio, nor any sort of an executable file in the library directory. What do I do? I will greatly appreciate any help you guys can offer on this.