You build apache with php statically linked instead of dynamically
linked.
Check the apache documentation on statically linking apache and php
(module).
I would venture to say that oracle libraries should not be shipped. They
are proprietary code and the user needs to install them. Your oracle
libraries should be installed by the user. However, I would suggest
checking with oracle on this.
--
Ray
On Wed, 2003-10-01 at 08:12, Donahue, Peter wrote:
How would I build them with all of the libraries?
Also - is it OK for me to ship Oracle libraries to
customers to install on a system that may not have
Oracle installed (tho they must have an Oracle server
installed somewhere in their network for the product
to actually do anything).
Thanks,
What you would want to do is build apache + php together with all the
libraries built into it. Unless you want the user to install the
libraries seperate. I have done this in the past however, you file is
going to be HUGE.
Basically you have a file with everything that it needs in it and does
not use any system libraries.
As for your questions: yes you can do it.
--
Ray
I want to build Php(4.3.3) for Apache(1.3.28) on Solaris 8.
I am configuring Php with oci8 (Oracle) support.
Is it possible to build Php on system A, and then move the
files over to another Solaris 8 system and expect it to function
properly? I expect there to be a problem with the ORACLE_HOME
path, if it's not the same on the second system. But I believe I should
be able to solve that by 'export'ing ORACLE_HOME in the
apachectl file.
What I'm trying to do is build Apache and Php so that I can ship them
and install them along with my product.
Thanks for any help
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
