Yup, in fact we should do that for all our bundled libraries. I wrote an
extension recently which relies heavily on our bundled version of the GD
library and since those header files are not installed you can only build
my extension by downloading the full PHP sources and pointing the build at
the
On Sun, 31 Aug 2003, Wez Furlong wrote:
>This is precisely what I am doing here (linking against libphp5 and using
>the exported sqlite symbols).
What if I build sqlite as shared? :)
>Would be nice if we could install just the sqlite.h file though as the
>others are internal to the library i
This is precisely what I am doing here (linking against libphp5 and using
the exported sqlite symbols).
Would be nice if we could install just the sqlite.h file though as the
others are internal to the library implementation.
--Wez.
> On Sun, 31 Aug 2003, Andi Gutmans wrote:
>
> > Why would you
On Sun, 31 Aug 2003, Andi Gutmans wrote:
> Why would you install the headers? It's not as if we're installing the .a
> or .so of sqlite (or are we?)
We're not, but we are exporting sqlite symbols from the bundled library,
so why not install the headers so people can make use of sqlite from
wit
Why would you install the headers? It's not as if we're installing the .a
or .so of sqlite (or are we?)
Andi
At 01:44 AM 8/31/2003 +, Wez Furlong wrote:
wez Sat Aug 30 21:44:46 2003 EDT
Modified files:
/php-src/scriptsMakefile.frag
Log:
install sqlite headers with
