Re: svn: /php/php-src/trunk/ ext/bz2/bz2.dsp ext/ctype/ctype.dsp ext/curl/curl.dsp ext/dba/dba.dsp ext/dom/dom.dsp ext/exif/exif.dsp
ext/ext_skel_win32.php ext/gd/gd.dsp ext/gettext/gettext.dsp ext/iconv/iconv.dsp ext/imap/imap.dsp ext/interbase/interbase.dsp ext/json/json.dsp
ext/ldap/ldap.dsp ext/mbstring/mbstring.dsp ext/mcrypt/mcrypt.dsp ext/mssql/mssql.dsp ext/mysql/mysql.dsp ext/mysql/mysql.mak ext/mysqli/mysqli.dsp
ext/oci8/oci8.dsp ext/openssl/openssl.dsp ext/openssl/openssl.mak ext/pgsql/pg
On Thu, 29 Apr 2010, Rob Richards wrote:
> The discussion was a while ago (Steph was working on a way to autogenerate
> them at the time). Unfortunately it failed miserably (buildconf error'd out)
> when I tried to use it (tried it after the dsps had been removed). Until that
> is working (or some other mechanism is in place to generate them), I see no
> reason to remove them. They easily convert to newer VS versions so not
> specifically for VC6. The project files are nice to have around for simple
> organization/access in VS especially since we already have them, so its not so
> much about using them to make a build as it is for the VS integration.
Can't we stick them in a dir under win32 or so? They're then not
"cluttering" the rest of the tree.
with kind regards,
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Thread (5 messages)