Lyndon Nerenberg wrote: > Why are parallel mkfiles in the /go tree considered eeevil? They seemed to > be very low overhead. Surely accomodations are being made for Windows. > > [...] My fiddling with the go tree makes me think it isn't that hard to > set up an overlay that adopts the live go tree to what Plan9 needs for a > build. bind(1) is a wonderful thing -- we should use it! > > [...] It can't be that hard > to parse out DIR= from there and turn it into a native mkfile.
I'm very late in the discussion, but I'd like to point out that Go is already using the go build tool instead of makefiles, at least for some part of the tree. I believe this simplifies things greatly. No makefiles to maintain or generate. -- Aram Hăvărneanu
