Re: Linking and autoloading of dependent extensions
| From: | Michael Wallner | Date: | Tue, 27 May 2014 15:30:09 +0000 |
| Subject: | Re: Linking and autoloading of dependent extensions | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74527@lists.php.net to get a copy of this message | ||
On 27 May 2014 16:25, "Johannes Schlüter" <johannes@schlueters.de> wrote:
>
> On Tue, 2014-05-27 at 16:11 +0200, Michael Wallner wrote:
> > >> * the extension is inside extension_dir and
> > >> * a specific naming scheme on the extension's shared library
file.
> >
> > Wait, what? I guess I read too fast. Did you see extensions not named
that way?
>
> I myself do this when keeping different versions around for testing etc.
> and I've even different (commercial) extensions doing that for
> distributing differently named files for different PHP versions.This
> also happens when handling mixed cased names vs. lowercase (i.e. if you
> build phar shared you get phar.so but it is called Phar, I assume there
> are others)
Well, ok... so that's absolutely not the problem I'm trying to solve. You
can still load that stubbornly named extensions manually and nothing will
complain, even if something has a dependency on it.
I'm about e.g. pecl install & going ahead without reordering extension
entries...
Cheers,
Mike