php embedded

[Captain Dondo]

I am working on an embedded platform which will serve a small number of
dynamic webpages. Right now we are looking at php+javascript with
apache as the webserver.

Do we need to compile the entire php tarball or is the php module in
apache enough to run php? Similarly, what is the minimum configuration
of php we need, assuming we only need to access flat-file ascii data?

Does anyone of any how-tos or guides for compiling php for embedded
platforms?

Thanks,

--Yan

[Justin Koivisto]

Captain Dondo wrote:

I am working on an embedded platform which will serve a small number of
dynamic webpages. Right now we are looking at php+javascript with
apache as the webserver.

Do we need to compile the entire php tarball or is the php module in
apache enough to run php? Similarly, what is the minimum configuration
of php we need, assuming we only need to access flat-file ascii data?

The first question is what is the embedded platform? (Windows, linux, etc.?)

If you are loading the php module for apache, you either have already
compiled the php source, or do not need to unless you need additional
features.

How do you plan on accessing the files? (which functions, etc.)

I'm betting that you'd be spending most of your time deciding which
extensions to *disable* rather than enable.

--
Justin Koivisto, ZCE - ju****@koivi.co m
http://koivi.com

[Captain Dondo]

Justin Koivisto wrote:

Captain Dondo wrote:

I am working on an embedded platform which will serve a small number of
dynamic webpages. Right now we are looking at php+javascript with
apache as the webserver.

Do we need to compile the entire php tarball or is the php module in
apache enough to run php? Similarly, what is the minimum configuration
of php we need, assuming we only need to access flat-file ascii data?

The first question is what is the embedded platform? (Windows, linux, etc.?)

Linux on arm, basically running a very stripped system.
If you are loading the php module for apache, you either have already
compiled the php source, or do not need to unless you need additional
features.
I guess my question is: "If I have the apache module, do I need any
other php-related stuff - libraries, modules, etc?"

How do you plan on accessing the files? (which functions, etc.)
All the PHP routines will do is read in a file, pre-fill a form, and
then write out the file based on form submission.

I'm betting that you'd be spending most of your time deciding which
extensions to *disable* rather than enable.
Exactly. I'm hoping someone has a guide out there on how to strip out
all those things I don't need...

[Justin Koivisto]

Captain Dondo wrote:

Justin Koivisto wrote:

Captain Dondo wrote:

I am working on an embedded platform which will serve a small number of
dynamic webpages. Right now we are looking at php+javascript with
apache as the webserver.

Do we need to compile the entire php tarball or is the php module in
apache enough to run php? Similarly, what is the minimum configuration
of php we need, assuming we only need to access flat-file ascii data?

The first question is what is the embedded platform? (Windows, linux,
etc.?)

Linux on arm, basically running a very stripped system.

If you are loading the php module for apache, you either have already
compiled the php source, or do not need to unless you need additional
features.

I guess my question is: "If I have the apache module, do I need any
other php-related stuff - libraries, modules, etc?"

Only if the code you write (or install) in PHP needs them. That would
then bring up more questions, of which the most important is:

Will the php code be embedded as well, or will others have the
opportunity to run their own code on this embedded system?

How do you plan on accessing the files? (which functions, etc.)

All the PHP routines will do is read in a file, pre-fill a form, and
then write out the file based on form submission.

Is this something similar to a firewall configuration? If so, then you
won't likely need other libraries or modules if the scripts don't need them.

I'm betting that you'd be spending most of your time deciding which
extensions to *disable* rather than enable.

Exactly. I'm hoping someone has a guide out there on how to strip out
all those things I don't need...

There won't be a guide as it will depend on the intended use (as per
above statements).

The way I'd go about this is to first compile the default configuration
and see what was enabled by viewing the output of php_info(). From
there, you should be able to "--without-PACKAGE" where necessary until
you think you have the minimum that your code needs. My suggestion about
this route is to disable no more than 2 or 3 extensions at a time and
test - especially if you didn't write the PHP code.

HTH

--
Justin Koivisto, ZCE - ju****@koivi.co m
http://koivi.com

[Chung Leong]

Captain Dondo wrote:

I am working on an embedded platform which will serve a small number of
dynamic webpages. Right now we are looking at php+javascript with
apache as the webserver.
What kind of hardware resources is available? Both PHP and Apache are
fairly large.
Do we need to compile the entire php tarball or is the php module in
apache enough to run php? Similarly, what is the minimum configuration
of php we need, assuming we only need to access flat-file ascii data?

It's been a while since I compiled PHP on Linux. I don't believe the
language core compiles into a separate dynamically loaded library as it
does on Windows. The Apache module should be all you need. There are a
number of extensions that are included by default. Look at the options
available to the autoconf script for more info. Around 400 functions
are bundled in the standard extension and cannot be removed without
altering the source. So even if you will never call highlight_sourc e()
or convert_cyr_str ing(), you're more or less stuck with them.

[C.]

"fairly large" - well yes. It sounds like this will not be a high
volume webserver, but with an ARM processor, there should be enough CPU
to get it running. I'd definitely consider ditching apache and using
thttpd or monkey or even one of the webservers written in PHP.

When I looked after production systems I prefered using prebuilt rpms
(along with a good upgrade tool) - it made management so much easier -
but I did build php5 with MySQL, GD, PECL and SQLLite. The stripped
binary was about 1Mb.

HTH

C.