Changes between Version 2 and Version 3 of Getting-Started/Running-Applications
- Timestamp:
- Apr 29, 2009 9:44:50 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Getting-Started/Running-Applications
v2 v3 1 1 = Running the Bundled Applications = 2 2 [[TracNav(Getting-Started/TOC)]] 3 [[PageOutline(2-3,,inline)]] 3 4 4 5 Upon successful build, the output libraries (PJLIB, PJLIB-UTIL, PJMEDIA, PJSIP, etc.) are put under ./lib sub-directory under each project directory. In addition, some applications may also be built, and such applications will be put in ./bin sub-directory under each project directory. 5 6 6 7 7 7.1 pjsua 8 == pjsua == 8 9 9 10 pjsua is the reference implementation for both PJSIP and PJMEDIA stack, and is the main target of the build system. Upon successful build, pjsua application will be put in pjsip-apps/bin directory. … … 12 13 13 14 14 7.2 Sample Applications 15 == Sample Applications == 15 16 16 17 Sample applications will be built with the Makefile build system. For Visual Studio, you have to build the samples manually by selecting and building the Samples project inside pjsip-apps/build/pjsip_apps.dsw project workspace. … … 21 22 22 23 23 7.3 pjlib-test 24 == pjlib-test == 24 25 25 26 pjlib-test contains comprehensive tests for testing PJLIB functionality. This application will only be built when the Makefile build system is used; with Visual Studio, one has to open pjlib.dsw project in pjlib/build directory to build this application. … … 28 29 29 30 30 7.4 pjsip-test 31 == pjsip-test == 31 32 32 33 pjsip-test contains codes for testing various SIP functionalities in PJSIP and also to benchmark static performance metrics such as message parsing per second.