[cfe-dev] [LLVMdev] zorg config for libc++/libc++abi
danalbert at google.com
Mon Aug 4 17:02:30 PDT 2014
Great, thanks! Can I assume that cmake and a relatively recent clang are
already installed? I can add building llvm/clang to the builder, but the
fewer CPU cycles the better.
Thanks. That write-up really helped. The process still sucks, but at least
I wasn't stumbling blindly.
On Mon, Aug 4, 2014 at 7:47 AM, Tobias Grosser <tobias at grosser.es> wrote:
> On 04/08/2014 16:20, Dmitri Gribenko wrote:
>> On Mon, Aug 4, 2014 at 2:20 PM, Dan Liew <dan at su-root.co.uk> wrote:
>>> Second, is there a simple way to test the builder and config before I
>>>> I am afraid not.
>>> But there is a ugly (and certainly not simple) way to partially test the
>>> builder that I mentioned recently .
>> Nice write-up!
>> I say partially because I ended up removing all the builders apart from
>>> @Dmitri - Has anyone considered reorganising zorg so it is easier to
>>> test a
>>> builder locally?
>> I am not aware of such effort. However, it would be great to be able
>> to easily set up a buildmaster locally. This will probably facilitate
>> further refactorings of zorg code. Currently developers tend not to
>> touch it because they can not run it.
> I commonly test my changes with a 'hacked' buildbot where references to
> non-existing files are removed and buildslave passwords are hardcoded.
> It would be great if we could instead have a 'testing' mode, where the
> user can provide a table with buildslave names and passwords and the
> buildbot just takes this to accept its buildslaves.
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev