Although I'm using VC2005, I also installed the Windows SDK 6.1 (which was the most current one at the time). It's official name is "Windows Software Development Kit (SDK) for Windows Server 2008 and .NET Framework 3.5", although I'm sure there are more current ones now (for Windows 7 if nothing else). I don't know if the enum problem was a one time fluke in this SDK or whether that's they way they intend to move forward with it, but soon I'll be updating my machine to Windows 7 and the latest tools, and I'll let you know then how Msoft is handling those constants (and of course anything else stupid they change that impacts pjsip). Thanks for the updates, it makes my life easier. --John pjsip-request at lists.pjsip.org wrote: Date: Thu, 15 Oct 2009 11:47:21 +0700 From: Benny Prijono <bennylp@xxxxxxxxx> Subject: Re: A couple of bug reports. To: pjsip list <pjsip at lists.pjsip.org> Message-ID: <49a4be80910142147p223567f8hc8c98a79fbbf552f at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi John, Sorry for the late reply. Please see comments inline. On Wed, Oct 7, 2009 at 10:08 PM, John Ridges <jridges at masque.com> wrote: > > Hi Benny, it's nice to see you back. > > > > Just a few quick bugs I wanted to report: > > > > Bug #1: PJ_SOL_TCP gives the wrong value in Windows. Or at least it does > > with my VC 2005 compiler. It seems that an "enum"ed symbol is not considered > > to be "#defined". Go figure. > > > Fixed in http://trac.pjsip.org/repos/ticket/972. Out of curiosity, which Platform SDK version do you use? I checked the SDK that comes with VS 2005 and VS 6 and they both have IPPROTO_TCP declared as macro.
