Okay, let me try to be explicit here. If I am leaving out any important
information, please just ask.
Environment:
OS X
uname -a:
Darwin host-29.dev.office.nexopia.com 9.2.2 Darwin Kernel Version 9.2.2:
Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386
with php-5.2.5.
What
On Apr 30, 2008, at 11:20 AM, Christopher Thompson wrote:
I don't want libphp.so as we are not using Apache.
The brief details are roughly as follows:
- we use lighthttpd for a web server
I have lighttpd running in OSX with PHP with quite a few extensions
as well so it's either your config
Paul Biggar wrote:
Hi Chris,
I'm very interested in having --enable-embed working on OS X. My
experience with libtool is that it abstracts this sort of thing, so
I'm a little bit confused by your work-around. Could you explain why
you added --enable-embed=dylib instead of fixing
--enable-embed=s
Hi Chris,
I'm very interested in having --enable-embed working on OS X. My
experience with libtool is that it abstracts this sort of thing, so
I'm a little bit confused by your work-around. Could you explain why
you added --enable-embed=dylib instead of fixing
--enable-embed=shared?
Thanks,
Paul
Although there's obviously some debate as to the usefulness of my embed
patch for OS X, here's a replacement for the Makefile.global bit. It
adds $(PHP_LDFLAGS) to the compile line for libphp5.dylib, necessary in
many cases.
--- php-5.2.5.clean/Makefile.global 2007-08-03 08:01:56.
I don't want libphp.so as we are not using Apache.
The brief details are roughly as follows:
- we use lighthttpd for a web server
- much of our site is in Php
- we are transitioning to Ruby
- we have a custom-written wrapper to allow Php to run inside of Ruby,
to make the transition a little eas
This is taken care of by "auto" tools.
If you are experiencing build issues of public releases then you're
doing something wrong.
I build PHP for a living in OS X and I've encountered no build issues
what-so-ever related to building with dylib linking but the resulting
binary will (should
shouldn't autotools take care about these differences?
On 4/30/08, Christopher Thompson <[EMAIL PROTECTED]> wrote:
> Please be gentle, I have very little experience developing on OS X. To be
> honest, the whole dylib thing seems messy and confusing to me, compared to
> the fairly straight-forward
Please be gentle, I have very little experience developing on OS X. To
be honest, the whole dylib thing seems messy and confusing to me,
compared to the fairly straight-forward Linux style .so approach.
Expected behavior:
Able to configure and build on OS X with:
./configure --enable-embed
A
