Changes between Version 13 and Version 14 of Getting-Started/Windows


Ignore:
Timestamp:
Apr 29, 2009 5:14:04 PM (10 years ago)
Author:
ismangil
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Getting-Started/Windows

    v13 v14  
    7171   5. Build and debug the project. 
    7272 
    73 == Using pjproject libraries for your own application == 
     73== Next: Using pjproject libraries for your own application == 
    7474 
    7575Regardless of the build system being used, the following tasks are normally needed to be done in order to build application to use PJSIP and PJMEDIA: 
     
    8181          * pjmedia/include 
    8282          * pjsip/include 
    83    2. Put these library directories in the library search path: 
    84           * pjlib/lib 
    85           * pjlib-util/lib 
    86           * pjnath/lib 
    87           * pjmedia/lib 
    88           * pjsip/lib 
    89    3. 
    90  
    91       Include the relevant PJ header files in the application source file. For example, using these would include ALL APIs exported by PJ: 
     83   2. Put the combined library directory '''lib''' in the library search path 
     84   3. Include the relevant PJ header files in the application source file. For example, using these would include ALL APIs exported by PJ: 
    9285         #include <pjlib.h> 
    9386         #include <pjlib-util.h> 
     
    10194 
    10295      (Note: the documentation of the relevant libraries should say which header files should be included to get the declaration of the APIs). 
    103    4. 
    104  
    105       Declare the OS macros. 
     96   4. Declare the OS macros. 
    10697          * For Windows applications built with Visual Studio, we need to declare PJ_WIN32=1 macro in the project settings (declaring the macro in the source file may not be sufficient). 
    10798          * For Windows Mobile applications build with Visual C++, we need to declare PJ_WIN32_WINCE=1 macro in the project settings. 
     
    109100 
    110101      (Note: the old PJ build system requires declaring the target processor with PJ_M_XXX=1 macro, but this has been made obsolete. The target processor will be detected from compiler's predefined macro by pjlib/config.h file). 
    111    5. 
    112  
    113       Link with the appropriate PJ libraries. The following libraries will need to be included in the library link specifications: 
     102   5. Link with the appropriate PJ libraries. The following libraries will need to be included in the library link specifications: 
    114103 
    115104      pjlib