Included freetype support for php
Why freetype support ?
If you compile PHP with gd and freetype[it's already a port], and grab
some free truetype fonts from microsoft in self-install.exe format you
can generate really nice on the fly gif's with text in them. Buttons,
banners etc.
William told me: I had to install the free microsoft fonts on my pc
and then ftp them. I can't think of a way to extract the files from
the .exe archive. I don't think it's a zip type.
I got the fonts microsoft link by digging around in
http://www.freetype.org
Submitted by: William Lloyd <wlloyd@mpd.ca>
fixes regarding compilation/linking with libgd
a fix for me in Makefile to make this submission $PREFIX clean
big thanks to William
Submitted by: William Lloyd <wlloyd@tolstoy.mpd.ca>
- now based on apache 1.2.6 and PHP3 support with the tough help of Dirk
- Supports 3 kinds of databases now
- msql
- mysql
- postgresql
- Only modified order in Makefile to keep portlint happy
- Fixed php's configure section in Makefile, to use CC and CFLAGS from
/etc/makefile, instead to use -g -O2
- only one patches subdir remains
This port should now be "repository moved" from:
apache-php
to something like:
apache12-php3
Obtained from: Dirk Froemberg <ibex@physik.TU-Berlin.DE>
New features:
- You have to set variable PHP_DBTYPE to msql or mysql by typing
make PHP_DBTYPE=[ msql | mysql ]
to build the port with msql or mysql support.
- The php configuration isn't interactive anymore
Theoretically we could default to mysql database and build
a package, so that make batch could work !
- Cleaned up port dependency, so that libgd actually gets build
(I fixed this one)
- made portlint as happy as I could, changed /usr/local to ${PREFIX}
and changed sed -> ${SED}
The only thing that is missing now is an apache-php-SSL port and
postgresql support ;-))
Submitted by: Dirk Froemberg <ibex@physik.TU-Berlin.DE>
Currently 2 kind of databases will be supported, msql and mysql
The problem is, that depending on the flavour of database you want
to support, you need a different set of patches to apache's
Makefile, so that header and loader flags, paths and libs
are correctly resolved ...
I marked this port as BROKEN, since I wasn't able, to exactly
check the whole port due to the fact, that currently I only
have one db installed. Will try to get it managed next weekend.
Well if someone is so keen, then simply remove BROKEN and you
should be able to use what's already possible ...
on the presence of SECURE_SERVER.
2) Clean up the installation in accordance with BSD religion:
Now all the configs go in ${PREFIX}/etc/apache and the
data (documents) stay in ${PREFIX}/www.
Remove pst's address from MAINTAINER, I don't know if any script
will fail if we have two addresses here so I don't want to risk
breaking something right before the release.
