Re: Re: I'd like to work on amfext
| From: | Gustavo Lopes | Date: | Tue, 27 Jul 2010 22:41:39 +0000 |
| Subject: | Re: Re: I'd like to work on amfext | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-7390@lists.php.net to get a copy of this message | ||
On Tue, 27 Jul 2010 22:35:02 +0100, j adams <zardozrocks@gmail.com> wrote:
Thanks for your response, Johannes! I'm in touch with Emanuele Ruffaldi, the current maintainer, and he's been encouraging. He recommended a setup involving Visual Studio which I'm a bit skeptical about: http://blog.slickedit.com/2007/09/creating-a-php-5-extension-with-visual-c-2005/Despite what that blog post says, I'd recommend you do indeed build PHP from source and just add your extension to the ext/ directory of the distribution. This wiki page will guide through the process: http://wiki.php.net/internals/windows/stepbystepbuild When you run buildconf, do instead buildconf --add-project-files This will create dsp files that you can then open in Visual Studio (I've only hit a small bug, I had to add ".." or "..\.." -- can't recall which -- to the include path of the extensions projects). All the shared extensions that you build will end up in a solution, one project per extension. This has several advantages: you get debug symbols for PHP itself without the shortcomings of the debug symbols for the release versions, and you also get a solution called "php5ts" with which you can easily explore the Zend API through Intellisense. There's also #php-dev-win @ freenode -- Gustavo Lopes