Re: [INTERNALS-WIN] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php-src(PHP_5_3) /win32/build DSP.README block.template.dsw buildconf.js config.w32
confutils.js projectgen.js template.dsp template.dsw
| From: | Rob Richards | Date: | Thu, 10 Jul 2008 14:36:41 +0000 |
| Subject: | Re: [INTERNALS-WIN] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php-src(PHP_5_3) /win32/build DSP.README block.template.dsw buildconf.js config.w32 confutils.js projectgen.js template.dsp template.dsw |
||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals.win |
| Request: | Send a blank email to internals-win+get-44@lists.php.net to get a copy of this message | ||
Steph Fox wrote:
Hi Rob, all,I see this as _part_ of fixing up the 5.3 build. We quite often get people checking out src, seeing .dsw and thinking it's going to be standard. We've had a number of unknown strangers grumble about the state of the .dsp files on-list after they've wasted time trying to get them to work. Making them generatable means we won't get that any more; it also means they'll always be up to date. The build/no-build question is less of an issue because it's always going to be possible to make the things build if the itch arises, it just means playing around with javascript a bit more. Well if you'll be able to get them buildable then I think its a non-issue then.I think it would actually be counter-productive to have them buildable, to be honest, but I'm willing to spend another day on it if what's there isn't good enough for the uses those files are put to. I wasn't sure whether project dependencies and include paths would be important in this regard, for example. If they're not, we're good to go with last night's efforts :)CC'ing him so he can chime in on this. Really though, with time getting short, we should be spending more time on the testing/fixing up of the 5.3 build and new libs than cosmetics.
http://pecl2.php.net/downloads/php-windows-builds/php-libs/No. Is this the famous pecl2 server that I'm not allowed involvement with? Beats me. As the libs in Edin's old zip.zip are completely outdated and things need to be brought up to date, the libs are currently being made available at:There wasn't a lot wrong with the 5.3 build until very recently. I'm getting all sorts of peculiar things now (GD failing to find libiconv, SimpleXML failing to find SPL, etc etc). But you've seen the response if I touch anything in that department.These are things that are more important imo. On to the other stuff though. First are you using all the new libs that will be used for the 5.3 build?
What error are you seeing with GD? I am no longer getting any build issues with GD since my zlib changes.iconv not found (everything else finds it), zlib redeclaration, no debug info in debug build, a few warnings. Appears not to be set to link against older iconv (not sure if thats intended or not). zlib stuff is fixed - should be at least. havent even looked at the debug info :)
failure to find SPL is not specific to either of those as it happens to all the extensions that recently are no longer optional to the build. The ADD_DEPENDS macro doesnt take this into account and because things are laid out alphabetically, SPL hasnt been defined yes when the SimpleXML checks are being done. Same thing happens with extensions like SDO (requiring SPL) and anything that requires reflection - and comes before reflection in the alphabet :)I could look into that one if you like. Please do. I just noticed it the other day but have plenty of other things that I could put my time to use on.
What else are you running into? I would be very interested to hear any problems so they can get resolved.Nothing I can't fix (hopefully). bz debug needs /nodefaultlib, mysqlnd and date are both riddled with VS6 cancer (heaps of warnings under debug). Nothing major. Good. Was afraid you were going to list of some major issues or something :)
RobAs far as you not touching the stuff, I don't think that's the case. I agree that some changes or ideas should be passed by the people on the list in case there are differing ideas for some of the larger changes, but fixing something is not wrong - as long as its made to HEAD too :).I still have: pecl/phar, HEAD/phar, some config/build stuff but I no longer know which because Pierre merged *some* of it, some phar-related stuff to do in SPL (in both HEAD and 5_3). Extension versioning if anyone can come up with a better idea than labelling everything x.x.x-core. That's less of an issue than in PECL because it makes good sense to have the core extension dlls built against a given version of PHP labelled with that version (e.g. in tile views etc), but it'd still be nice to have some sanity in phpinfo(). So then for the windows 5.3 specific stuff, what do you expect would be doable by end of month - my guesstimate for the timeframe.