Hi, Ahh, I'm sorry for my ignorance, the library for Winsock 2 is ws2_32.lib. The first error should go with this. For the second one make sure you are linking to ole32.lib (Hmm, I wonder why you didn't get errors for CoCreateInstance and other COM API's before this, maybe the linker didn't try further after getting this error?). As of closing the thread, I guess road blocks like this happen with everyone, so we can try to help a bit. But, as a side note you should try to use the tools that are meant to be used with a particular library. And, VC++ 2005 is a standard C++ compilant compiler. You should be able to build all standard C++ projects with it. Maybe you were just getting some weird errors that needed subtle changes in configuration of VC++ 2003. Thanks. Best Regards, Hitesh ----- Original Message ----- From: "Eagle I Martin Baranski" <eagle3386@xxxxxxxxxxxxxx> To: "pjsip embedded/DSP SIP discussion" <pjsip at lists.pjsip.org> Sent: Sunday, November 11, 2007 1:10 PM Subject: Re: Win32 build doesn't build because of stddef.h > 2007/11/10, logan <logan04x at gmail.com>: >> Hi, >> >> Try wsock32.lib, look for it on your disk and include the path in your >> linker directories. If you can't find it then it's available with the MS >> Platform SDK. >> >> Thanks. > > Hi Hitesh, > > thanks for your hint - got it insert (although I additionally had to > insert the absolute path of the library into the linker's options, > too).. > > So now, I only remain with 2 errors (instead of more than 50): > > M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(sock_bsd.o): In > function `pj_sock_socket': > M:/pj-sip/pjlib/src/pj/sock_bsd.c:347: undefined reference to > `WSASocketA at 24' > M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(guid_win32.o): In > function `pj_generate_unique_string': > M:/pj-sip/pjlib/src/pj/guid_win32.c:69: undefined reference to > `CoCreateGuid at 4' > collect2: ld returned 1 exit status > Process terminated with status 1 (0 minutes, 8 seconds) > 2 errors, 0 warnings > > > Benny, > > I'm just thinking that the GCC should be supported, because that's > definitely a better compiler than MS' one.. I'm saying this, because I > had to work with VS 2003 .NET some time ago and especially the linker > was pure pain to me.. It threw errors where GCC worked just fine - and > GCC is stricter than MS' linker.. > And since the compiler works fine and the IDE does what it's meant to > be, I don't see any reason for switching over to the > Code::Blocks-forums. > Instead, IMHO it's more a putting-pjsip-into-a-gcc-compatible-form-stuff.. > ;) > > > Roland, > > although this might be hard to understand, I want to say that this is > what makes me still saying "code is poetry" - all this hard work will > finally work and then, there's kind of silence and pleasure and what > I'm feeling in that moment is just awesome.. > You know, that's this "still standing, fighting with the code and > finally win the battle".. > > So, why close this topic as the final step is already in sight? > > > Regards, > Martin.. > -- > ===================== > = ~ Code is poetry ~ > ===================== > = Martin Baranski > = Eagle | Eagle3386 > = www.troublezone.net > = eagle3386 at gmail.com > = +49 (0)160 93317843 > ===================== > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
