Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25827
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.182.187 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=AUhzD2127TuH10VWUmE89gAeBeSc6xkOaY6gy0p1vWQzOBjmvZPKeVkvwSrQ48EooKtXImqBUtZjlkDJv/FsQPIuafZGkz5fQWDNWCVQU2pY1FvNv5jpAAWqhIm7Vu+w74dlbN1G4p+/2y/I0J7ozz3OCoHjDWIlpPmHNy/jqoA=
Message-ID: <451845A3.4010901@gmail.com>
Date: Mon, 25 Sep 2006 22:09:55 +0100
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To:  internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Building C++ extensions
From: stuttle@gmail.com (Stut)

Ok, so I've built an extension that uses a C++ library. It compiles fine 
but the build system is insisting on linking with gcc no matter what I 
tell it. Is there some simple trick I'm missing as far as convincing it 
to use g++ goes?

Here is the config.m4 in case I've missed something in there...

PHP_ARG_ENABLE(mmsr, whether to enable mmsr support,
[  --enable-mmsr=dir       Enable mmsr support])

if test "$PHP_MMSR" != "no"; then
   PHP_ADD_LIBRARY_WITH_PATH(mmsr, "$PHP_MMSR")
   PHP_ADD_INCLUDE("$PHP_MMSR/MMSR")
   PHP_NEW_EXTENSION(mmsr, mmsr.c "$PHP_MMSR/MMSR/mmsr_bridge.cpp", 
$ext_shared)
   PHP_REQUIRE_CXX()
fi

I had expected the PHP_REQUIRE_CXX() macro to trigger a change to the 
link command, but it does not seem to have done anything beyond 
influencing what is used to compile the extension itself.

-Stut