Lines Matching refs:extensions
20 * Installation of PECL extensions
22 + Downloading PECL extensions
24 + Compiling shared PECL extensions with the pecl command
25 + Compiling shared PECL extensions with phpize
27 + Compiling PECL extensions statically into PHP
218 various options, like which extensions will be enabled. Run
250 8. Tell Apache to parse certain extensions as PHP. For example, let's
310 all extensions will be available. The recommended setup is to build
643 extensions'.
659 compiling PHP (and related extensions) on HP-UX systems has been
707 PHP 4 port is split into two sub-directories: core and extensions. The
708 extensions directory generates sub-packages for all of the supported
763 For building extra extensions or hacking the code of PHP you might also
942 3. Be sure the desired extensions will parse as PHP (examples: .php
1006 Installation of PECL extensions
1011 * Downloading PECL extensions
1013 * Compiling shared PECL extensions with the pecl command
1014 * Compiling shared PECL extensions with phpize
1016 * Compiling PECL extensions statically into PHP
1021 » PECL is a repository of PHP extensions that are made available to you
1023 to demonstrate how to obtain and install PECL extensions.
1033 how to build and install the extensions, but they do not automatically
1044 Downloading PECL extensions
1046 There are several options for downloading PECL extensions, such as:
1047 * The pecl install extname command downloads the extensions code
1051 the different extensions that are offered by the PHP Development
1054 * pecl download extname PECL extensions that have releases listed on
1057 * SVN Most PECL extensions also reside in SVN. A web-based view may
1063 Windows binaries for PECL extensions. However, to compile PHP under
1075 your system. All the extensions are automatically and periodically
1088 PHP extensions are usually called "php_*.dll" (where the star
1090 "PHP\ext" ("PHP\extensions" in PHP 4) folder.
1092 PHP ships with the extensions most useful to the majority of
1093 developers. They are called "core" extensions.
1098 directory of all known extensions and hosting facilities for
1099 downloading and development of PHP extensions.
1133 php.ini configuration file. Please note that many extensions are
1174 Compiling shared PECL extensions with the pecl command
1176 PECL makes it easy to create shared PHP extensions. Using the » pecl
1202 Compiling shared PECL extensions with phpize
1207 as unreleased extensions from SVN. If you need to build such an
1222 PHP extensions directory. You'll need to and adjust php.ini and add an
1229 extensions.
1240 When compiling extensions, if you have multiple PHP versions installed,
1268 --extension-dir Directory where extensions are searched by default
1280 Compiling PECL extensions statically into PHP
1419 The php.ini directives handled by extensions are documented on the
1420 respective pages of the extensions themselves. A list of the core
1600 5. Unix: I patched Apache with the FrontPage extensions patch, and
1602 FrontPage extensions?
1721 Unix: I patched Apache with the FrontPage extensions patch, and
1723 Apache FrontPage extensions?
1724 No, PHP works fine with the FrontPage extensions. The problem is
1784 php.ini or any PHP extensions you are trying to load are such
