diff options
Diffstat (limited to 'pjlib/include')
-rw-r--r-- | pjlib/include/pj/doxygen.h | 17 | ||||
-rw-r--r-- | pjlib/include/pj/pool.h | 3 |
2 files changed, 18 insertions, 2 deletions
diff --git a/pjlib/include/pj/doxygen.h b/pjlib/include/pj/doxygen.h index 51a69777..855d3312 100644 --- a/pjlib/include/pj/doxygen.h +++ b/pjlib/include/pj/doxygen.h @@ -55,7 +55,7 @@ * * @subsection doc_ver_subsec Version * - * This document corresponds to PJLIB version 0.5.7.6. + * This document corresponds to PJLIB version 0.5.8. * * * @subsection find_samples_subsec How to Read This Document @@ -457,6 +457,14 @@ * * @section build_sys_install_sec Build and Installation * + * \note + * <b>The most up-to-date information on building and installing PJLIB + * should be found in the website, under "Getting Started" document. + * More over, the new PJLIB build system is now based on autoconf, + * so some of the information here might not be relevant anymore + * (although most still are, since the autoconf script still use + * the old Makefile system as the backend).</b> + * * @subsection build_sys_install_win32_sec Visual Studio * * The PJLIB Visual Studio workspace supports the building of PJLIB @@ -793,6 +801,13 @@ obj-$(CONFIG_GENERIC_ISA_DMA) += dma.o /** * @page porting_pjlib_pg Porting PJLIB * + * \note + * <b>Since version 0.5.8, PJLIB build system is now based on autoconf, so + * most of the time we shouldn't need to apply the tweakings below to get + * PJLIB working on a new platform. However, since the autoconf build system + * still uses the old Makefile build system, the information below may still + * be useful for reference. + * </b> * * @section new_arch_sec Porting to New CPU Architecture * diff --git a/pjlib/include/pj/pool.h b/pjlib/include/pj/pool.h index 48c00e8e..61c3de09 100644 --- a/pjlib/include/pj/pool.h +++ b/pjlib/include/pj/pool.h @@ -101,7 +101,8 @@ PJ_BEGIN_DECL * The result of PJLIB's memory design and careful implementation is a * memory allocation strategy that can speed-up the memory allocations * and deallocations by up to <b>30 times</b> compared to standard - * malloc()/free()! + * malloc()/free() (more than 150 million allocations per second on a + * P4/3.0GHz Linux machine). * * (Note: your mileage may vary, of course. You can see how much PJLIB's * pool improves the performance over malloc()/free() in your target |