The Xdebug extension helps you debugging your script by providing a lot of
valuable debug information. The debug information that Xdebug can provide
includes the following:
* stack and function traces in error messages with:
o full parameter display for user defined functions
o function name, file name and line indications
o support for member functions
* memory allocation
* protection for infinite recursions
Xdebug also provides:
* profiling information for PHP scripts
* script execution analysis
* capabilities to debug your scripts interactively with a debug client
WWW: http://www.xdebug.org/
devel/php-xdebug -> devel/pecl-xdebug
Using pecl instead that a legacy way to build the extension
Reviewed by: olivier
Sponsored by: trivago N.V.
Differential Revision: https://reviews.freebsd.org/D13825
Don't use extension.ini any more, and have each extension install in its
file, so the order remains the same.
Every PHP (or Zend) extension now installs its own .ini file in
/usr/local/etc/php. A PHP extension will be automatically activated
when installed. The order into which extensions are loaded is
automatically guessed. In some very rare cases, the guess will be
wrong, and PHP_MOD_PRIO will need to be set. Refer to the USES=php
section of the Porter's Handbook for more information.
Convert ports touching etc/php/extensions.ini manually, or telling the
OP to do it.
And finally, bump PORTREVISION for all php extensions.
PR: 210697
Submitted by: mat
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D7022
These ports do not build with PHP 7.0, make them as such.
Also, mark those who try to use mysql, which does not exist in PHP 7.0.
Sponsored by: Absolight
- Configure as a Zend extension rather than a normal php extension
PR: ports/182916
Submitted by: Kimo <kimor79@yahoo.com>
Approved by: maintainer timeout (freebsd-ports-maintainers@intermedix.com, >2
months)
Do not force DEFAULT_PHP_VER to version 5, let bsd.php.mk figure it out.
This allows xdebug to work with all PHP versions again.
PR: ports/170614
Approved by: maintainer timeout
Update to 2.2.0 and work on php54.
PR: ports/168583
Submitted by: Oleg Ginzburg <olevole@olevole.ru>
Approved by: Bill Moran <wmoran@collaborativefusion.com> (maintainer)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
