There is an impedence mismatch here between typical usage on Unix and
typical usage on Windows. Some infomation that can typically be compiled-in
on Unix must be determined at runtime on Windows.
I don't believe the environment is really a good place to be expecting this
information - not on Wind
Yu are right. Two of the values needs to be constants, as these are used
in building the INI array.
Setting the constants to this works:
#define PEAR_INSTALLDIR
(getenv("PEAR_INSTALLDIR"))?getenv("PEAR_INSTALLDIR"):"c:\\php4\\pear"
#define PHP_BINDIR (getenv("PHP_BINDIR"))?getenv("PHP_BINDIR"):"
On Sun, 01 Dec 2002 07:57:18 -0800
"Frank M. Kromann" <[EMAIL PROTECTED]> wrote:
> We could change it to something like this:
>
> #define PEAR_INSTALLDIR
> (getenv("PEAR_INSTALLDIR"))?getenv("PEAR_INSTALLDIR"):"c:\\php4\\pear"
As far as I remember, that s what has been done weeks ago and causes
We could change it to something like this:
#define PEAR_INSTALLDIR
(getenv("PEAR_INSTALLDIR"))?getenv("PEAR_INSTALLDIR"):"c:\\php4\\pear"
#define PHP_BINDIR (getenv("PHP_BINDIR"))?getenv("PHP_BINDIR"):"c:\\php4"
#define PHP_CONFIG_FILE_PATH
(getenv("PHP_CONFIG_FILE_PATH"))?getenv("PHP_CONFIG_FILE_
On Sun, 1 Dec 2002 09:48:35 -0500
Dan Kalowsky <[EMAIL PROTECTED]> wrote:
>Sounds like an interesting idea, but does this:
> A) accurately reflect the changes you want to do (I think the #defines
> are messed up)
They are here, but useless ;-)
> B) work at all on a pre-built binary?
I do not b
