Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.82.50 as permitted sender)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <6AB80FC7-3E7D-4EFE-B1AA-5C19D3351267@googlemail.com>
Date: Fri, 7 Nov 2014 19:26:01 +0100
To: PHP internals list <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: How are plugins built on OS X?
From: ingwie2000@googlemail.com ("Kevin Ingwersen (Ingwie Phoenix)")

Hey.

While I am creating a small build tool and learning more about Clang/GCC =
and the various linkers, I came across the differences between =
shared/dynamic libraries, plugins and executables on the various =
platforms. That made me wonder, how PHP=E2=80=99s plugins are compiled.

For instance, if one had `enable-curl=3Dshared` turned on, with the CGI =
and CLI SAPI, we=E2=80=99d get two binaries and a shared object - a =
=E2=80=9Ebundle=E2=80=9C on OS X. But, there are two ways to compile =
php_curl.so :

	-bundle -bundle_loader /path/to/php
or
	-bundle -undefined dynamic_lookup

Both are only needed if unresolved symbols occur, though. In my test-run =
with a plugin framework, I ran into this issue. By Apple=E2=80=99s docs, =
one basically needs -bundle and =E2=80=9Eflags and switches that one =
would use during the compilation of an executable=E2=80=9C.

Which of the above methods are mainly used for PHP=E2=80=99s shared =
extensions? I would go and try and dig my way thru Make and =
Autoconf/phpize - but my make-fu is far beyond what I would need here, =
only to find one single answer. :)

Kind regards, Ingwie=