Errr what? Now I speak with 13 years experience with software development so don't tell me I'm not on top of my build environment just because you read the beginning of a path name and made an assumption to its contents. The fact of the matter is I can't get libSSH2 to compile following the instructions that come with it, end of story.
For your information I was trying to do an x64 build of linCURL, and following an article I was reading it said that I needed to use libSSH2. Now as I was building it as a proof of concept for someone else I put all related projects into a root project called libCurl_X64. That clearly makes sense. I suggest you try treating people with a little respect rather than attempting to insult them due to your own mistakes. Thankfully I don't need it now, which is good because I won't have to be dealing with people like you! ------------------------------ Message: 3 Date: Mon, 17 Sep 2012 16:02:03 +0200 From: Peter Stuge <pe...@stuge.se> To: libssh2-devel@cool.haxx.se Subject: Re: Compiling libssh2 under x64 with Visual Studio 2010 Message-ID: <20120917140203.4604.qm...@stuge.se> Content-Type: text/plain; charset=us-ascii Nick Pateman wrote: > They aren't CURL errors, they are libssh2 errors, I just have the > source in a folder named libCurl_X64 or whatever lol. You must obviously use separate projects for building separate software, and it usually helps to use separate directories. You are clearly not on top of your build environment, there's nothing we can do to help with that. > Thankfully I've managed to get around needing libSSH2, the article I > was reading was misleading so I'm all sorted now. libcurl will work without libssh2, but with limited functionality. You need to know what suits your needs, and you need to build each software accordingly.. //Peter _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
