OK, let me clarify what I'm talking about:
There are several dll's that are sitting in a folder called extensions when you
download the binary for windows. Those dll's STAY WHERE THEY ARE as long as you
specify that they are there in the php.ini file. i.e... d:\php\extensions
There are a TOTALLY SEPARATE set of dll's that are sitting in the folder called
"dll's" when you download the binary:
expat.dll
fdftk.dll
gds32.dll
gnu_gettex.dll
jvm.dll
libpq.dll
just to list a few. They WILL NOT work if you leave them in that folder. They are
the dll's for windows that actually run their corresponding dll that is sitting in the
php folder. Try it. If you leave them in the folder d:\php\dll's and set the php.ini
to use fdf's, you will get an error on your phpinfo() page that says it can't find the
fdf dll. EVen though there is a fdf.dll in extensions, it won't work without the
fdftk.dll. SOOOO, whoever wrote the install document for php windows knew it would
work if you put it in c:\winnt\system32. However, I spoke with the original developer
of php for windows and he said he never promoted that practice. He told me it worked
but it wasn't desirable to mess with your system folder. The other place you can put
the dll's for the "dll's" folder is in the same folder where php.exe resides. As far
as I know, unless you do specific altering to windows environmental variables, those
are the only two places you can put those dll's that php can see them. So...for
clarification for everyone in case I've confused more than helped:
LEAVE the dlls sitting in the extensions folder there, and give the path to them in
you php.ini file.
Copy all the dll's that are sitting in the "dll's" folder and paste them one directory
up, in your php folder where php.exe is sitting. That is STRAIGHT from the mouth of
Shane Caraveo. If you disagree with the creator, or have a better option, contact him
at Active State and maybe he can put it in the new documentation he makes for the next
php for win release.
Angie
>>> "Svensson, B.A.T. " <[EMAIL PROTECTED]> 08/19/01 11:18AM >>>
I don't understand what you are talking about now.
How set an access path is irrelevant in this case. That's not
the point. The point is that information should be as accurate
as possible. You stated that a DLL needed to be located at an
certain location. That is simply not ture at all.
Cheers,
Anders
>-----Original Message-----
>From: Angie Tollerson [mailto:[EMAIL PROTECTED]]
>Sent: Friday, August 17, 2001 6:21 PM
>To: [EMAIL PROTECTED]; Svensson, B.A.T.
>Subject: RE: [PHP-WIN] Image Functions
>
>
>Right Anders, you could simply set the access path in
>environmental variables for windows itself. But for newbies
>just installing the easiest thing to tell them is to put it
>either in system folder or php folder, php folder being the
>better choice.
>
>Angie Tollerson
>Alliance Technologies
>Web Programmer
>(515)245-7628
>[EMAIL PROTECTED]
>
>>>> "Svensson, B.A.T. " <[EMAIL PROTECTED]> 08/17/01 11:16AM >>>
>>The extension dll's do need to stay in the extension folder
>>with the right .ini line as you stated. I'm talking about the
>>system needed dll's that come in the DLL folder. Those are
>
>From an functional point of view, it really doesn't matter were
>a DLL is located, as long as it located in the access path. But
>from a point of view with the organization of the file system in
>mind it might though matter.
>
> /Anders
>
>--
>PHP Windows Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail:
>[EMAIL PROTECTED]
>
>
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
