On 7/3/2011 1:52 PM, William A. Rowe Jr. wrote: > > The answer is generating them from build.py etc, just as we generate > the makefiles from config.m4. In fact the right clues embedded in > config.m4 files might let us use these as sources ;-)
And I'm willing to build the apr build.py features and config.m4 parser (with some dnl WIN32: hints logic to work around the prickly stuff) over the month of July. I have some work stuff I have to wrap up in the coming days, but then I'll jump on it. If everyone likes the result, we'll purge the dsp/dsw/generated mak/dep files (except for using a -win32-src.zip file which would pre-run the py scripts). The working solution should be a smaller tarball, since vc6 generated mak files include quite a bit of cruft. Mladen, do you know anything of cl.exe's ability to generate dependencies? I've never looked before.
