Subject: Re: Visual C++ 2010 Express edition cannot open and convert libssh2 win32 project file

Re: Visual C++ 2010 Express edition cannot open and convert libssh2 win32 project file

From: Noah <n0ahz0rk_at_gmail.com>
Date: Tue, 04 Sep 2012 21:08:03 +1000
Thanks Alex, works perfectly, and I have been able to build libcurl as per the guide I referred to before with the libssh2.lib generated via the method you described below.

Just in case there are any other noobs like me using visual c++ express, you can create a static library project by selecting a win32 console app as the main template (as there is no template for static library), then on the subsequent screen, you will see a radio button option to select a static library instead of the console app.
On 4/09/2012 7:57 PM, Alexander Lamaison wrote:
On 4 September 2012 04:49, Noah <n0ahz0rk@gmail.com> wrote:

Hi,

Not sure if others have this problem, but I have tried to open the
C:\libssh2-1.4.2\win32\libssh2.dsp file (as per the instruction in Andrei
Jakab's Using libcurl with SSH support in Visual Studio 2010 [PDF] -
referring to the link on http://curl.haxx.se/libcurl/c/ ) with my Visual C++
2010 Express edition, and I do get the prompt that advises the project will
have to be converted, but after that I get no error messages, and no project
is open in the IDE.

I can't help you with the conversion but my advice would be to ignore
the included project files entirely as libssh2 is so easy to build on
Windows.  Here's the guide I sent round the list a little while back:

Using Visual Studio:
- Shove all the .c files in libssh2/src into an empty Win32 C++ (DLL
or Static Library) project except libgcrypt.c/openssl.c of which you
only pick the one appropriate to your crypto library.
- Add your OpenSSL or libgcrypt include directory to the project include path
- Add libssh2/include to the project include path
- Add libssh2/win32 to the project include path
- Add the appropriate crypto libraries to the project Additonal Libraries list
- Build
- Job done

Using MinGW:
I'm not confident enough to list the exact steps for this but its
basically a matter of adding the same .c files to a Makefile source
list and instructing gcc to make a DLL or static library from them.
Use Google to find the flags you need to add for those two
alternatives.

Alex

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2012-09-04