Re: Command line compilation under win32
| From: | Edin Kadribasic | Date: | Fri, 17 May 2002 13:38:14 +0000 |
| Subject: | Re: Command line compilation under win32 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-84140@lists.php.net to get a copy of this message | ||
> I'm in the process of getting a more permanent win32 build environment
sorted
> out, and one of the things I'd like to do is avoid the VS IDE as much as
> possible, and automate builds so that I can test changes that I make under
> unix. (Perhaps even by rshing to my win32 box).
>
> I know it's possible to build projects from the command line using
something
> like "msdev xxx.dsw", but so far I've not succeeded (and have little
patience
> with win32 and the command line, because it is generally quite limited).
Hi Wez,
After you installed your win32 build environment as specified in
http://www.php.net/manual/en/install.windows.php#install.windows.build
change directory to win32 in your php source tree and issue:
cmd /c msdev php4ts.dsp /MAKE "php4ts - Win32 Release_TS"
(I use cygwin bash shell for all command line work, so cmd /c is required)
This will make php4ts.lib, php4ts.dll and php-cgi.exe. If you want to
compile cli after that:
cmd /c msdev php4ts_cli.dsp /MAKE "php4ts_cli - Win32 Release_TS"
In order to build extension change to the ext dir (in this example bz2)
cd ext/bz2
cmd /c msdev bz2.dsp /MAKE "bz2 - Win32 Release_TS"
You should now have php_bz2 in ../../Realease_TS
One more thing: mdev recognizes some env variables like INCLUDE and LIB
specifying what gcc would take under -I and -L options. In oder to make
msdev use these add /USEENV to the command line.
Hope this gets you starded. You're welcome to write to me if you stumble
across any problems.
Edin