The obvious solution to the problem is to have the installer take care of this
in the first place.
I would be _more_ than happy to help in this regard. I've spent a little time
doing this sort of thing and would be more than happy to help out.
What we need to remember is the point of view of the developer and the
end-user. The developer wants to keep the projects seperate so he/she can have
an easier time debugging.
Round up the troops, figure out the best method for both sides. I'd be more
than happy to write an installer that keeps us all in business.
Deal?
Angie Tollerson wrote:
>
> hehe...I think that was my original advice in the whole long email discussion that
>stemmed this. (check Image Functions thread). The most straight forward and simple
>solution for everyone is to just put all those files together in one place. But if
>others want to go the more advanced route(which keeps dll's neatly in their own
>folder), I think Craig was just offering how to for anyone wondering.
>
> >>> Phil Driscoll <[EMAIL PROTECTED]> 08/21/01 05:05AM >>>
> Surely the ideal solution to this problem is to have php.exe php4ts.dll and
> all the other dlls in the same directory (e.g. c:\php) then there's no
> messing around with paths?
--
Craig Morrison
MTS Professional @ http://www.2cah.com/
A Win32 Email server that works for _you_.
EzMTS - A _free_ Win32 EMail Server
http://www.ezmts.org/
Anonymous FTP at ftp://ftp.ezmts.org
--
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]
