Hi, I would like to back this up. With the .dsp files there is too many hardcoded parameters that you need to make sure is up to date, and it requires headers and libraries to be in specific places. With the new build system you can organize your files almost as you wish and it is much easier to create a version of php with the extension that you need, even without the need to change files.
- Frank > > I don't really mind how the snapshots are built but it is crucial for > > Windows development to keep the .dsp's working and up-to-date. It's the > > only sane way to develop & debug on Windows. > > You can still use the VC++ or VS.Net IDE to debug and write code using > the new build system. > > One of the motivations for the build system is that it is more difficult > than it needs to be to keep those .dsp files up to date - for example, > there are a number of them that have inconsistent defines and paths set > for different targets (Debug_TS and Release_TS) and some of those targets > for some projects won't even work at all. > > One of the Zend projects won't correctly regenerate a scanner or parser > unless you build with a particular target first, before switching to > the target you need (I don't recall the precise details, but you can > see this by looking at the custom build steps for flex/bison in the dsp). > > I know that people tend to stick to what works well for them, > but hopefully you'll all get converted over to the new build system > so that we can eventually drop those .dsp files ;-) > > --Wez. > > -- > PHP CVS Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
