Changes between Initial Version and Version 1 of Getting-Started/Running-Applications

Timestamp:

Apr 28, 2009 5:06:13 PM (16 years ago)

Author:

ismangil

Comment:

--

Getting-Started/Running-Applications

@@ +1 @@
+= Running the Applications =
+[[TracNav(Getting-Started/TOC)]]
+
+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.
+
+ 
+7.1 pjsua
+
+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.
+
+pjsua manual can be found in pjsua Manual Page.
+
+ 
+7.2 Sample Applications
+
+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.
+
+Upon successful build, the sample applications are put in pjsip-apps/bin/samples directory.
+
+The sample applications are described in PJMEDIA Samples Page and PJSIP Samples Page in the website.
+
+ 
+7.3 pjlib-test
+
+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.
+
+If you're porting PJLIB to new target, it is recommended to run this application to make sure that all functionalities works as expected.
+
+ 
+7.4 pjsip-test
+
+pjsip-test contains codes for testing various SIP functionalities in PJSIP and also to benchmark static performance metrics such as message parsing per second.
+
+