Hi, there is a script (in PHP) that removes the mobile targets for you. And VS2010 build works very well then. See http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2013-April/016086.html Cheers, - Vali ______________________________________________________________ > Od: Bill Gardner <billg at wavearts.com> > Komu: <pjsip at lists.pjsip.org> > Datum: 20.02.2015 15:45 > P?edm?t: Re: [pjsip] How to build pjsip in VS2010 > >Hi Antonio, > >Thanks for that. I'm pretty sure the conversion to 2010 fails because of >the Pocket PC and Windows Mobile platforms. You can manually edit the >project files and remove all reference to those platforms and >configurations, then save and open in 2010. The conversion should work. >However, like all conversions from 2008 to 2010, the output targets may >need tweaking because 2010 uses a different build system. > >Regards, > >Bill > >On 2/20/2015 3:07 AM, Antonio Sedano Maestre wrote: >> >> Hello, >> >> I have been working with pjsip the last weeks and it was necessary for >> us to build the pjsip library in VS2010, at the end I have found this >> solution. I hope this was useful for someone else. >> >> How to build PjSip in Visual Studio 2010. (PJSIP Versi?n 2.3) >> >> 1st-> Download the version from Pjsip.org >> >> 2nd-> open the solution from visual studio 2012 or 2013. This is >> because the migration in Visual Studio 2010 does not work fine. >> >> 3rd-> Copy the solution to the computer where you have Visual Studio >> 2010. If you have installed vs2010 and vs2012 in the same computer >> after the conversion to vs2012, >> >> vs2010 will tell to you cannot open the solution owing the >> solution belong to a newer VS version. >> >> 4th-> Open the Solution in the computer where you have VS2010. >> Remember, you have to create config_site.h file in ...\include\pj. >> >> 5th-> At this point, if you Build the solution you are going to have >> the next error in Iphlpapi.h (windows sdk 7.0A header): >> >> "Error before );" >> >> If you click over the error, iphlpapi.h file is going to appear >> in this point >> >> #if (NTDDI_VERSION >= NTDDI_XP) >> >> ULONG >> >> WINAPI >> >> GetIpStatisticsEx( >> >> __out PMIB_IPSTATS Statistics, >> >> __in ULONG Family >> >> ); >> >> The error is because NTDDI_XP does not exit. The right >> define is NTDDI_WINXP, so you must change NTDDI_XP for NTDDI_WINXP. >> Only in #if (NTDDI_VERSION >= NTDDI_WINXP) >> >> 6th->After all of this, the lib is going to be building without >> problem, but the sample project can have problem with nmake to be >> built. You can try to solve this problem, >> >> but for me, it was easier to create a new Win32 c++ project and >> paste in the .cpp file the code of the sample that you want. >> >> Note: If you want to use the pjsip library within in a C++ managed >> project you have to write the next lines where you reference to >> #include <pjsua-lib/pjsua.h>: >> >> .h file >> >> #pragma once >> >> #include "Stdafx.h" >> >> #ifdef __cplusplus >> >> extern "C" >> >> { >> >> #endif >> >> #include <pjsua-lib/pjsua.h> >> >> #ifdef __cplusplus >> >> } >> >> #endif >> >> //TODO: write here your includes >> >> #include "Logs.h" >> >> #include "ImMessage.h" >> >> //TODO: write here your using >> >> using namespace System; >> >> using namespace Runtime::InteropServices; >> >> #pragma comment (lib, "Ws2_32.lib") >> >> Regards. >> >> logo_neatelectronics >> >> >> >> Antonio Sedano Maestre >> >> *NEAT Group ? Software Department* >> >> Calle del Espino, 14 - Urb. Monteprincipe - 28668 Boadilla del Monte - >> Madrid >> >> Tlf. 902 365 748 Fax 91 535 08 89 >> >> asedano at gruponeat.com <mailto:asedano at gruponeat.com>www.gruponeat.com >> <http://www.gruponeat.com/> >> >> >> >> _______________________________________________ >> 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 > > > >---------- > >_______________________________________________ >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 >
