Re: pecl building on win32

The new win32 build system solves these problems; pecl extensions just need to define a config.w32 file using similar syntax to config.m4 files. I wouldn't worry too much about building win32 extensions from source using the pear installer anyway; php requires way too much stuff to expect anyone but hard-core developers to be able to build things "out-of-the-box" - and in that case, they will be happier using the configure.js script directly (it automatically picks up an existing pecl checkout from CVS and merges the config.w32 files into configure when you run buildconf.bat) --Wez. ----- Original Message ----- From: "Greg Beaver" <greg@chiaraquartet.net> To: <pecl-dev@lists.php.net> Sent: Monday, December 15, 2003 11:12 PM Subject: [PECL-DEV] pecl building on win32 > Hi, > > The PEAR_Builder class is horribly out of date for win32, I've just > taken a stab at fixing it up, and have found a few huge problems. First > of all, VC++ .NET 2003 doesn't have "msdev.exe", but could use nmake > with an exported makefile. Second, the .dsp files I have seen all make > assumptions about the locations of header files for php > (..\..\..\php4\Zend, for example), and I don't see any immediate way to > change this very easily without parsing the .dsp files at install-time. > > I think the simplest solution might be to wait until channels are > implemented in the PEAR installer, and have separate PECL sub-channels > for source and compiled binaries, so that windows users can do whatever > setup they might need for installation of pecl pre-built binaries, or at > their option, set up a few configuration variables to point at the > location of php source (these would need to be added to the PEAR core).