Changeset 514 for pjproject/trunk/pjlib/include/pj/doxygen.h
- Timestamp:
- Jun 16, 2006 4:52:51 PM (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
pjproject/trunk/pjlib/include/pj/doxygen.h
r513 r514 235 235 * 236 236 * 237 * @subsection hl_network_io_sec High-Level Network I/O238 *239 * At higher abstraction, PJLIB provides @ref PJ_IOQUEUE,240 * which promotes creating high performance network241 * applications by managing asynchronous I/O. This is a passive framework242 * that utilizes the most effective way to manage asynchronous I/O243 * on a given platform, such as:244 * - IoCompletionPort on WinNT,245 * - on Linux it can use either /dev/epoll or aio.246 * - or to fall back to use @a select()247 *248 * At even a higher abstraction, PJLIB provides @ref PJ_EQUEUE, which249 * combines asynchronous I/O with timer management and thread management250 * to fasilitate creating trully high performance, event driven251 * application.252 *253 237 * 254 238 * @subsection timer_mgmt_sec Timer Management … … 485 469 * several choices on which \a dsw file to open: 486 470 \verbatim 487 $PJPROJECT/build/pjproject.dsw 488 $PJPROJECT/pjlib/build/pjlib.dsw 489 $PJPROJECT/pjsip/build/pjsip.dsw 471 $PJPROJECT/pjlib/build/pjlib.dsw 472 $PJPROJECT/pjsip/build/pjsip.dsw 490 473 ..etc 491 474 \endverbatim 492 475 * 493 * The easiest way is to open <tt>pjproject.dsw</tt> file in \b \c $PJPROJECT/build 494 * directory. However this will only build the required projects, not 495 * the complete projects. For example, the PJLIB test and samples projects 496 * are not included in this workspace. To build the complete projects, you must 476 * The easiest way is to open <tt>pjsip_apps.dsw</tt> file in \b \c $PJPROJECT/pjsip-apps/build 477 * directory, and build pjsua project or the samples project. 478 * However this will not build the complete projects. 479 * For example, the PJLIB test is not included in this workspace. 480 * To build the complete projects, you must 497 481 * open and build each \a dsw file in \c build directory in each 498 482 * subprojects. For example, to open the complete PJLIB workspace, open … … 568 552 * 569 553 \verbatim 570 $ cd /home/user/pjproject # <-- go to $PJPROJECT571 $ vi build.mak # <-- set build target etc554 $ cd /home/user/pjproject 555 $ ./configure 572 556 $ touch pjlib/include/pj/config_site.h 573 $ cd pjlib/build # <-- go to projet's build dir574 $ make # <-- build the project557 $ make dep 558 $ make 575 559 \endverbatim 576 560 * 577 * For other project, \a cd to <tt>build</tt> directory in the project 578 * and execute \a make from there. 561 * The above process will build all static libraries and all applications. 562 * 563 * \note the <tt>configure</tt> script is not a proper autoconf script, 564 * but rather a simple shell script to detect current host. This script 565 * currently does not support cross-compilation. 579 566 * 580 567 * \note For Linux kernel target, there are additional steps required, which 581 568 * will be explained in section \ref linux_kern_target_subsec. 582 569 * 583 * @subsubsection build_mak_sec Editing build.mak570 * @subsubsection build_mak_sec Cross Compilation 584 571 * 585 * The \c build.mak file in \c $PJPROJECT root directory is used to 586 * specify the build configuration. This file is expected to export 587 * the following \a make variables: 588 * 589 * - <tt><b>MACHINE_NAME</b></tt> 590 *\n 591 * Target machine/processor, one of: <b>{ i386 | alpha | sparc }</b>. 592 * 593 * - <tt><b>OS_NAME</b></tt> 594 *\n 595 * Target operating system, one of: <b>{ win32 | linux | 596 * linux-kernel | sunos }</b>. 597 * 598 * - <tt><b>CC_NAME</b></tt> 599 *\n 600 * Compiler name: <b>{ gcc | vc }</b>\n 601 * (Note that support for Visual C (vc) compiler with the \c make system is 602 * experimental, and it will only work when run inside a DOS shell 603 * (i.e. <tt>"HOST_NAME=win32"</tt>)). 604 * 605 * - <tt><b>HOST_NAME</b></tt> 606 *\n 607 * Build host: <b>{ unix | mingw | win32 }</b>\n 608 * (Note: win32 host means a DOS command prompt. Support for this type 609 * of development host is experimental). 610 * 611 * These variables will cause the correct configuration file in 612 * \c $PJPROJECT/build directory to be executed by \a make. For 613 * example, specifying \c OS_NAME=linux will cause file \c os-linux.mak 614 * in \c build directory to be executed. These files contain specific 615 * configuration for the option that is selected. 572 * For cross compilation, you will need to edit the \c build.mak file in 573 * \c $PJPROJECT root directory manually. Please see <b>README-configure</b> file 574 * in the root directory for more information. 616 575 * 617 576 * For Linux kernel target, you are also required to declare the following
Note: See TracChangeset
for help on using the changeset viewer.