search for: faod

...ly seems to be moving away from autoconf toward CMake. Is there a reason why you need the autoconf build bad enough to support it out-of-tree? The reasons a short-term and boring engineering/project-related, rather than ideological. We all agree that one well-maintained build system is desirable; FAOD I have no axe to grind over which it is - providing it supports the hosts, targets and use-cases we care about. > Today supporting LLD’s autoconf build out-of-tree probably isn’t that bad because LLD is fairly small and LLVM still has a functioning autoconf build system. However, if LLVM moves...

...is as I understand the consensus from our conversation. The concrete protocol is my own invention. Please comments. After a round of review here we should consider whether some of the assumptions need review from the communities involved in "other" backends (particularly, the BSDs). (FAOD the implementation of something like this is not 4.3 material, but it may inform some API decisions etc. we take in 4.2.) Ian. Components toolstack guest Might be the toolstack domain, or an (intended) guest vm. driver domain Responsible for providing the disk service to guests....

I fixed the immediate problem - please let me know when you are going to break my build so I can switch to maintaining it locally. thanks Iain ] On 13 Mar 2015, at 17:04, Rui Ueyama wrote: > Looks like most developers prefer Makefile removal, and there's no push-back. Let's go ahead and remove them. I'll send a patch. > > On Wed, Mar 11, 2015 at 3:33 PM, Iain Sandoe <iain