I fixed the issue by rebuilding libcurl for 64 bit. The issue was related to using wdk 64 bit checked build environment, with a 32 bit build of curl.
I retargeted the build for 64 bit and built it as c. Everything from there was great. From: [email protected] To: [email protected] Subject: linker error with wdk Date: Tue, 12 Jun 2012 14:14:51 +0000 Hi All, Having scanned around I can see that the linker error issues are fairly common, but so far I haven't been successful using people solutions. I have a driver, written using wdk. An original version 32 bit runs perfectly with libcurl, (using libcurl_imp.lib and related dll). The only modifications I needed to make was adding __cdecl to certain functions due to mangling. It recently came to light that the driver now needs to be used with Server 2008 R2 64 bit. The driver has been ported to 64 bit and compiles, but I am now getting the classic linker errors: imp_curl_easy.. not found. As far as I can tell this error occurs when the driver is expecting static linking. So I added a #define CURL_STATICLIB and setup the sources files to target the static libs, but the linker error then just states : curl_easy... (just removing the imp) At this stage I am considering moving over to wininet - -but I would prefer not to! Does anybody have any experience with using libcurl under wdk? Apologies for the slightly vague question - I have config and code samples as may be required, and full compiler outputs/settings if need be. Best, G ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
