bing swen wrote: > > So is it a good idea to maintain two sets of project files to cope with this > problem: one for the old VS 5/6 .dsp files (no more x64 support), and one for > VS 2005/08 .vcproj files (with direct x64 support)?
No, it's a horrid idea. It's a good idea to drop to one cross-platform reference file as apr has (config.layout), and spit out whatever the heck the user wants (visual studio .dsw, .sln, eclipse, codewarrior etc etc.) Right now windows users are treated to a gui perspective of httpd (which I'll state firsthand is an amazingly better way to become acquainted with the code base) while unix users stumble in makefile land of ./configure --help. But the number one problem at httpd builds has always been that the .dsp falls out of sync with makefile.in and config.m4, while the netware build is often not updated for half a year. That's what happens when we appeal to each special interest of their own unique build system. So my holiday project is to resolve apr for win32 from config.layout etc. (If Netware wasn't an orphaned platform, I'd even likely start replacing their files too, but I'll let someone interested in orphans start dealing with that). Once successful, going to look at doing the same over here. And likely will stick with config.m4 files as best as I can, since love them or hate them, they are what we are used to.
