I've cross posted to the windows list as this is a useful link!
I don't feel quite so bad now about not being able to update my own builds, but
a matching Additional Extensions section for the x86 builds would just finish
the picture.
I'm just waiting for an OK to use the links in my own tutorials.
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Lester,
We are now all aware of your constant bashing about our work for php
on windows, but could you please give us some rest and post this
wherever you like.
And no you won't get a official ok for this build or any other but
what we have already numerous times discuss. The same applies even
more for x64 versions.
Thanks for your understanding,
I've cross posted to the windows list as this is a useful link!
I don't feel quite so bad now about not being able to update my own builds,
but a matching Additional Extensions section for the x86 builds would just
finish the picture.I'm just waiting for an OK to use the links in my own tutorials.
--
Lester Caine - G8HFLContact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php--
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
Pierre Joye wrote:
Lester,
We are now all aware of your constant bashing about our work for php
on windows, but could you please give us some rest and post this
wherever you like.And no you won't get a official ok for this build or any other but
what we have already numerous times discuss. The same applies even
more for x64 versions.
No problem ... I'm not asking ... but future Firebird builds will only work
fully with 64 bit installations.
If anybody is interested
http://enquirysolve.co.uk/wiki/index.php?page=Windows+Manual+-+FWAP+Installation
replaces the one from 2006 which can't be used now to carry out a current
working install.
Still very much work in progress - I've been working on this since last night -
I need to sort out how to unzip the php files on Windows 7 - I said no to the
RAR trial and did not ralise that it also kills zip handling! :(
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Pierre Joye wrote:
Lester,
We are now all aware of your constant bashing about our work for php
on windows, but could you please give us some rest and post this
wherever you like.And no you won't get a official ok for this build or any other but
what we have already numerous times discuss. The same applies even
more for x64 versions.No problem ... I'm not asking ... but future Firebird builds will only
work fully with 64 bit installations.
I can see it making sense to have a 64-bit build of a Database, but
clients that just talk to it over a socket using some socket protocol
shouldn't in any way be required to also be 64-bit. Same goes for your
Web server and PHP if you use the recommended FastCGI mechanism. Again
there is a nice separation between the two, so you don't need to match
build environments there either.
-Rasmus
I don't feel quite so bad now about not being able to update my own builds, but a matching Additional Extensions section for the x86 builds would just finish the picture.
If the PHP+Windows community developed a reliable system that built [most] all PECL extensions, then we would link to that within the PHP Manual. And if such a system was moved to a php.net server, then DLL download links could also be added to each individual pecl.php.net page.
Regards,
Philip
I don't feel quite so bad now about not being able to update my own builds, but a matching Additional Extensions section for the x86 builds would just finish the picture.
If the PHP+Windows community developed a reliable system that built [most] all PECL extensions, then we would link to that within the PHP Manual. And if such a system was moved to a php.net server, then DLL download links could also be added to each individual pecl.php.net page.
There is an easy way to build pecl extension and yes, pecl.php.net
will be the place to provide them as well. In the meantime I uploaded
them in the link I pasted earlier. But it happens that things can
happen when people actually do the work, and not only complain
endlessly in all possible channels.
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
I don't feel quite so bad now about not being able to update my own builds, but a matching Additional Extensions section for the x86 builds would just finish the picture.
If the PHP+Windows community developed a reliable system that built [most] all PECL extensions, then we would link to that within the PHP Manual. And if such a system was moved to a php.net server, then DLL download links could also be added to each individual pecl.php.net page.
There is an easy way to build pecl extension and yes, pecl.php.net
will be the place to provide them as well. In the meantime I uploaded
them in the link I pasted earlier. But it happens that things can
happen when people actually do the work, and not only complain
endlessly in all possible channels.
And this is a call for someone or some people to do the work by raising a hand, posting an RFC, writing code, whatever it takes. But I think people assume either it's going to eventually happen, or that php.net is happy with the current situation. In other words, we need an official progress report and position on the manner. Thoughts?
Regards,
Philip
And this is a call for someone or some people to do the work by raising a hand, posting an RFC, writing code, whatever it takes. But I think people assume either it's going to eventually happen, or that php.net is happy with the current situation. In other words, we need an official progress report and position on the manner. Thoughts?
There is an official report and that's phpize support being almost
complete, that finally two persons seem to be willing to help with the
web frontend parts of the job. Wiki sections with the progress will
follow as well. So please do not interfere with that as it could be
finally take off and the last we need is even more confusions and
politics. Once it is place, I will make the change in the docs
accordingly.
But about linking some random, uncontrolled and especially ones
provided by the initial poster in this thread in our documentation is
an absolute no go. The reasons are numerous and quite obvious if you
have followed the archives.
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
And this is a call for someone or some people to do the work by raising a hand, posting an RFC, writing code, whatever it takes. But I think people assume either it's going to eventually happen, or that php.net is happy with the current situation. In other words, we need an official progress report and position on the manner. Thoughts?
There is an official report and that's phpize support being almost
complete, that finally two persons seem to be willing to help with the
web frontend parts of the job. Wiki sections with the progress will
follow as well. So please do not interfere with that as it could be
finally take off and the last we need is even more confusions and
politics. Once it is place, I will make the change in the docs
accordingly.
My intent is to push progress and gain clarity.
But about linking some random, uncontrolled and especially ones
provided by the initial poster in this thread in our documentation is
an absolute no go. The reasons are numerous and quite obvious if you
have followed the archives.
I'm happy to hear progress is being made.
Regards,
Philip