Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74090
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <964B0802-BCEF-4A11-8660-B2E9DA592B9C@saxonica.com>
References: <42E6A56D-0FF1-4408-BCF5-DFBCEDA735EB@saxonica.com>
	<1396445137.2982.291.camel@guybrush>
	<2EF10AD3-FC2C-4F34-9639-8BC798DB0917@saxonica.com>
	<1396449767.2982.294.camel@guybrush>
	<40B86AC1-3057-4016-95E2-EB8E754A70E1@saxonica.com>
	<d20f098a37c1d74127feae4381dc4f80.squirrel@webmail.klapt.com>
	<C1479AA7-B398-4320-BAF0-A8B6F9355DC3@saxonica.com>
	<57711604dc923c34412021350230d52e.squirrel@webmail.klapt.com>
	<B17A80E7-043B-4D1C-9CD6-BAA4123A73BB@saxonica.com>
	<CAEZPtU46ThC6xwGvCciuXUNCH9NXbjxPHi_5k++cZ0OBHNjgvg@mail.gmail.com>
	<964B0802-BCEF-4A11-8660-B2E9DA592B9C@saxonica.com>
Date: Fri, 9 May 2014 13:41:00 +0200
Message-ID: <CAEZPtU7KvZhpmn2ZDZ-8VmiEo8qsC=iL_AqTFnq7AuCNdnz+Ow@mail.gmail.com>
To: "O'Neil Delpratt" <oneil@saxonica.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP C++ extension on Windows
From: pierre.php@gmail.com (Pierre Joye)

On Fri, May 9, 2014 at 12:06 PM, O'Neil Delpratt <oneil@saxonica.com> wrote=
:
>
> On 9 May 2014, at 10:26, Pierre Joye <pierre.php@gmail.com> wrote:
>
>> hi,
>>
>> On Fri, May 9, 2014 at 11:20 AM, O'Neil Delpratt <oneil@saxonica.com> wr=
ote:
>>> Hi,
>>>
>>> Is there a better way to build a PHP C++ extension for PHP 5.5 than in =
Visual studio? I know it can be done in the PHP build process for windows a=
s described in the book =E2=80=9CExtending and Embedding PHP=E2=80=9D by Sa=
ra Golemon which I did try but failed with linking errors, maybe because of=
 the config.w32 file not being setup properly. Under linux I have no issues=
.
>>
>> Actually the better and recommended way is not to use VS but for debuggi=
ng.
>>
>> See https://wiki.php.net/internals/windows/stepbystepbuild
>
>
> How about building your own extension? There seems to be a lack of inform=
ation about doing that on windows

same, copy it to the ../pecl/ directory, run buildconf etc.

You can use phpize too if your exts do not have dependencies against
other extension.

The process is also described in the wiki

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org