On Tue, 28 May 2013 18:19:57 -0700 Brad Roberts <[email protected]> wrote: > > Ignore what may or may not exist outside the current make files. > Just start with what exists in them. Soon after there are workable > targets to the existing makefiles, I'll get the auto-tester to > execute them and upload the results to s3 and make them public. > > I really don't think the zip/tarball creation steps should be a > separate script. A while back I started putting together a proof of > concept / strawman version of what I was thinking. They're likely > somewhat bitrotten, but look at my account on github in the dmd, > druntime, and phobos repos. There's an 'install' branch for each of > them with a commit or two to each. > > I stopped when I git the documentation as the build systems for them > are absurdly complex and convoluted. Additionally, the tools stuff > needs work, though its been ages since I last looked at them. >
While that may be a feasible approach, IMO I think it's worth minimizing the amount of work D's infrastructure needs to do in shell, batch and makefile scripting. Compared to D itself, those tend to be less portable (most notably the Win/Posix rift), more difficult to write/maintain, and less graceful with unexpected failures. Plus there's the increased dogfooding and the whole "self-hosted bragging rights" thing that some people value. _______________________________________________ dmd-beta mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-beta
