php-windows Digest 25 Sep 2005 09:18:52 -0000 Issue 2784
Topics (messages 26376 through 26378):
unresolved _core_globals_id question
26376 by: Alexey A. Rybak
Visibility of the root in an APACHE setting
26377 by: Tony Aldemir
26378 by: Darvin
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
hi, all
i'm trying to build my php-5.0.5 extension under XP with VC++ 6.0, but at
the link stage i always get
error LNK2001: unresolved external symbol _core_globals_id
..\..\Release_TS/php_blitz.dll : fatal error LNK1120: 1 unresolved externals
Error executing link.exe.
how can i fix this error?
the same code was built without any problems on lunux.
thanx
wbr,
Alexey A. Rybak
--- End Message ---
--- Begin Message ---
A rookie question:
Whenever I download and unzip any PHP related solution, the term "unzip it
to your web server's document root" is used. I am using APACHE and my doc
root is the default "C:\Program Files\Apache Group\Apache2\htdocs".
Now if I put all of the PHP code I develop as well as I download into a
single directory, I will have a major file soup soon, which can't be good.
I am sure there is a way to organize my files under the root in different
folders or somewhere else and still have them visible to the APACHE server.
What is the trick here?
Any help will be greatly appreciated.
Regards,
Tony
--- End Message ---
--- Begin Message ---
Tony Aldemir wrote:
A rookie question:
[...]
I am sure there is a way to organize my files under the root in different
folders or somewhere else and still have them visible to the APACHE server.
What is the trick here?
The easiest way is to unzip the application into its own dir (say appX)
into the htdocs, then from your browser point to http://yousite/appX.
Another way is to unzip the applications somewhere on your system, then
tell to apache how to reach that application using the parameter 'alias'
(i.e. alias /appX/ "your_disk:/path_to_appX/" ). From the browser
point of view this solution is the same as the previous
(http://yousite/appX points to appX).
Both solutions may be broken if the application points at least one page
to the site root (/somescript.php). You may handle that case using the
vitrual host. Each virtual host may have its own home directory.
Tony
Darvin
--- End Message ---
