Changeset 6 for pjproject/main/pjlib/include/pj/doxygen.h
- Timestamp:
- Nov 2, 2005 12:50:58 PM (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
pjproject/main/pjlib/include/pj/doxygen.h
r4 r6 10 10 */ 11 11 12 /*////////////////////////////////////////////////////////////////////////// */12 /*////////////////////////////////////////////////////////////////////////// */ 13 13 /* 14 14 INTRODUCTION PAGE … … 442 442 * - i386/Linux 443 443 * - i386/Linux (kernel) 444 * 445 * Generally, steps required to build the projects are: 444 * - alpha/linux 445 * - sparc/SunOS 446 * - etc.. 447 * 448 * 449 * @subsubsection build_req_sec Requirements 450 * 451 * In order to use the \c make based build system, you MUST have: 452 * 453 * - <b>GNU make</b> 454 *\n 455 * The Makefiles heavily utilize GNU make commands which most likely 456 * are not available in other \c make system. 457 * - <b>bash</b> shell is recommended. 458 *\n 459 * Specificly, there is a command <tt>"echo -n"</tt> which may not work 460 * in other shells. This command is used when generating dependencies 461 * (<tt>make dep</tt>) and it's located in 462 * <tt>$PJPROJECT/build/rules.mak</tt>. 463 * - <b>ar</b>, <b>ranlib</b> from GNU binutils 464 *\n 465 * In your system has different <tt>ar</tt> or <tt>ranlib</tt> (e.g. they 466 * may have been installed as <tt>gar</tt> and <tt>granlib</tt>), then 467 * either you create the relevant symbolic links, <b>or</b> modify 468 * <tt>$PJPROJECT/build/cc-gcc.mak</tt> and rename <tt>ar</tt> and 469 * <tt>ranlib</tt> to the appropriate names. 470 * - <b>gcc</b> to generate dependency. 471 *\n 472 * Currently the build system uses <tt>"gcc -MM"</tt> to generate build 473 * dependencies. If <tt>gcc</tt> is not desired to generate dependency, 474 * then either you don't run <tt>make dep</tt>, <b>or</b> edit 475 * <tt>$PJPROJECT/build/rules.mak</tt> to calculate dependency using 476 * your prefered method. (And let me know when you do so so that I can 477 * update the file. :) ) 478 * 479 * @subsubsection build_overview_sec Building the Project 480 * 481 * Generally, steps required to build the PJLIB are: 446 482 * 447 483 \verbatim 448 $ cd /home/user/pjproject -0.3 # <-- go to $PJPROJECT\n449 $ vi build.mak # <-- set build target etc \n450 $ cd pjlib/build # <-- go to projet's build dir \n451 $ make # <-- build the project \n484 $ cd /home/user/pjproject # <-- go to $PJPROJECT 485 $ vi build.mak # <-- set build target etc 486 $ cd pjlib/build # <-- go to projet's build dir 487 $ make # <-- build the project 452 488 \endverbatim 453 489 * … … 464 500 * the following \a make variables: 465 501 * 466 * - \c MACHINE_NAME 467 *\n 468 * Target machine/processor, one of: <b>{ i386 }</b>. 469 * 470 * - \c OS_NAME 471 *\n 472 * Target operating system, one of: <b>{ win32 | linux | linux-kernel }</b>. 473 * 474 * - \c CC_NAME 475 *\n 476 * Compiler name: <b>{ gcc | vc }</b> 477 * 478 * - \c HOST_NAME 479 *\n 480 * Build host: <b>{ unix | mingw }</b> 502 * - <tt><b>MACHINE_NAME</b></tt> 503 *\n 504 * Target machine/processor, one of: <b>{ i386 | alpha | sparc }</b>. 505 * 506 * - <tt><b>OS_NAME</b></tt> 507 *\n 508 * Target operating system, one of: <b>{ win32 | linux | 509 * linux-kernel | sunos }</b>. 510 * 511 * - <tt><b>CC_NAME</b></tt> 512 *\n 513 * Compiler name: <b>{ gcc | vc }</b>\n 514 * (Note that support for Visual C (vc) compiler with the \c make system is 515 * experimental, and it will only work when run inside a DOS shell 516 * (i.e. <tt>"HOST_NAME=win32"</tt>)). 517 * 518 * - <tt><b>HOST_NAME</b></tt> 519 *\n 520 * Build host: <b>{ unix | mingw | win32 }</b>\n 521 * (Note: win32 host means a DOS command prompt. Support for this type 522 * of development host is experimental). 481 523 * 482 524 * These variables will cause the correct configuration file in … … 534 576 \endverbatim 535 577 * 578 * Alternatively you may invoke <tt>make</tt> in <tt>$PJPROJECT</tt> 579 * directory, to build all projects under that directory (e.g. 580 * PJLIB, PJSIP, etc.). 536 581 * 537 582 *
Note: See TracChangeset
for help on using the changeset viewer.