stipus, Yes, that does it; thank you. I tried this before and failed, but it's easy to forget one library when there are so many and most have multiple configurations.
For others who try this: - remember to change all the configurations for each project, or at least all the ones you plan to use (if you change them all then you won't have to know which ones are being used) - when building the Debug configuration, you will need to rebuild cppunitd.lib with the same configuration change - if you get an error like "The operation could not be completed. Unspecified error" from Visual Studio when trying to get the properties for a project, try changing the configuration and trying again. For some projects (like libgsm-msvc8 and sipXportLibTest-msvc8) Visual Studio apparently chokes if the selected configuration is not available in the project for which you're trying to display the properties dialog - if you miss one project/library, Visual Studio will also try to link in the DLL runtime libraries, and will fail - if you need to figure out which project/library is referring to a DLL library (MSVCRT.LIB / MSVCPRT.LIB or MSVCRTD.LIB / MSVCPRTD.LIB), turn on verbose linker messages (project properties, Configuration Properties, Linker, General, Show Progress) and check the build output - this Microsoft knowledge base item explains the many different libraries used for Visual C++ programs: < http://support.microsoft.com/kb/154419/ > - some of the projects (such as libspeex) put both Debug and Release builds in the same folder with the same name. This means you must rebuild the solution if you change the configuration. Finest regards, Bill Root At 8/27/2008 10:31 AM, you wrote: >For each project within sipxtapi, select properties / general / C++ / Code >generation, and for the "Runtime library" entry, choose Multi-Threaded (/MT) >instead of Multi-Threaded DLL (/MD). > >I never tried, but this "should" be the right way to achieve your goal. >Don't forget to change this parameter on all sipxtapi projects (sipxtapi, >portlib, calllib, stacklib, medialib...) > >Regards, > >stipus > >-----Message d'origine----- >De : stipus [mailto:[EMAIL PROTECTED] >Envoyé : mercredi 27 août 2008 09:19 >À : '[email protected]' >Objet : RE: [sipxtapi-dev] Deployed sipXtapi Windows app fails with >0xc0150002 > >You need to install the VS2005 SP1 redistribution package on the deployment >computer. >You can easily download this from the MS download site. > >This installs new versions of the side by side MSVC runtime libs. > >Best regards, > >stipus > >-----Message d'origine----- >De : [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] De la part de Bill Root >Envoyé : mercredi 27 août 2008 01:43 >À : [email protected] >Objet : [sipxtapi-dev] Deployed sipXtapi Windows app fails with 0xc0150002 > > >My application using sipXtapi.dll under Windows fails with the >following error message in a relatively clean Windows XP VM: > "The application failed to initialize properly >(0xc0150002). Click on OK to terminate the application." > >A short Google search suggests the app wants a Visual C++ 2005 SP1 >Redistributable Package (x86). I am using Visual C++ 2005 to build >sipXtapi.dll. Is there a build switch, setting or option to prevent >sipXtapi from requiring more Microsoft crud? I never used Visual C++ >2005 before my foray into sipXtapi so I'm really hoping I overlooked >something. > >Thanks! > >Finest regards, >Bill Root > >_______________________________________________ >sipxtapi-dev mailing list >[email protected] >List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ > > > > >_______________________________________________ >sipxtapi-dev mailing list >[email protected] >List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
