Re: [INTERNALS-WIN] Re: php_yaz php5.3.5 windows

[email protected] (Richard Quadling)
Newsgroups php.internals.win
Message-ID <[email protected]>
On 21 March 2011 13:32, Michael Ridinger <[email protected]> wrote:
> One thing I'm confused about is the compiling process itself.
>
> I can compile PHP successfully but I'm not sure how to compile a PECL
> package.  I just don't understand how to do that?  I've read literally
> dozens of tutorials on how to setup the environment to compile PHP, which
> I've done successfully, but then they stop short ot describing how to
> compile a PECL package.
>
> Can it be compiled into PHP 5.3.5 or can it be compiled into a DLL I can use
> for an extension or can both be done?  I'm just not real familiar with doing
> these types of things.  I don't even know how the file structure should be
> setup.  And, it gets even more frustrating when I download the win32 PECL
> packages and find that YAZ isnt there so I have to get it with CSV.  I'm
> just missing some key pieces.
>
> I appreciate any way you can help.
>
> Mike
>
> On Sun, Mar 20, 2011 at 4:56 PM, Michael Ridinger <[email protected]>wrote:
>
>> I've been using php_yaz for a long time with PHP 5.1 and 5.2.  I've had to
>> setup a new server for another reason and am now using Windows 2008R2 and
>> PHP5.2.17 or PHP5.3.5 with IIS7 and am having absolutely no luch getting the
>> php_yaz package to build.  In fact, I can't get any package to build.  I can
>> build PHP, but not any PECL packages and am totally stumped.  I tried
>> following directions/docs everywhere I could find them and still have not
>> been able to build this extension.
>>
>> In the past, I've been able to download the extension and use it but it's
>> not part of the PHP distribution and PECL doesn't have it as a binary... so,
>> I have to the building myself.
>>
>> Anyone know how to do this effectively?  This is very important to me.  I
>> need php_yaz for Windows2008 and from what I've read, I need to compile it
>> using VC9, which I did.  The one issue that's really threw me is that
>> PHP5.3.5 doesn't run as an ISAPI module but with fast-cgi.  That makes the
>> package a little funky to deal with as it requires PHP5ts.dll, which isn't
>> part of PHP5.3.5 or PHP5.2.17.
>>
>> Obviously I'm a novice at building such things... I'm a developer, but not
>> a package builder.  Can anyone help or show me how to do this ... or at the
>> very least point me in the right direction?
>>
>> Thank you
>>
>> Mike
>>
>

Create a directory that is parallel to your php code.

I have

L:\BuildPHP\php53dev\vc9\x86
  deps
  Patches
  pecl
  PHP_5_3

In pecl, create a directory for the extension. It will need to contain
the code from trunk, the branch or the tag that you want to compile.

e.g.

L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\tests
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\CREDITS
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\README
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\php_yaz.c
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\yaz.dsp
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\php_yaz.h
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\config.m4
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\config.w32
L:\BuildPHP\php53dev\vc9\x86\pecl\yaz\package.xml
etc.

When you run buildconf, the configuration of the extensions in pecl
will be found.

You can then include/exclude them via the configure.js script.

If you run ...

configure --help

you'll see (for yaz) ...

  --with-yaz                        YAZ support (ANSI/NISO Z39.50)

So, you can now say ...

configure --with-yaz=shared

(for example - missing out a lot of other options).

And when you then run nmake, you'll get yaz compiled.

I've not tried it (as I'm a bit slow on these things), but there is a
mechanism called phpize which I think it a process to compile a PHP
extension without the need to do a full build of PHP.

Richard.

-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.