We've been looking at setting up a windows buildbot too. However from my end
the docs on setting one up are a little light on actual detail needed for a
sysadmin to work with :) we don't have a problem providing licences for the
machine.
Even one that tested simply building without running tests would be a great
step in the right direction!
Colin
-----Original Message-----
From: "Virgile Bello" <[email protected]>
Sent: 15/03/2014 12:38
To: "Greg Clayton" <[email protected]>
Cc: "lldb-dev" <[email protected]>
Subject: Re: [lldb-dev] Are the JITLoaderGDB and ProcessElfCore pluginssupposed
to work on OS X?
Concerning builds, I try to always check against cmake and make (Windows +
Linux), but I noticed many of the LLDB build bots are not in very good shape.
Also, not sure if there is buildbots are testing automake & xcode only, or if
some of them are testing cmake build as well? (even for LLVM?)
If buildbot gets fixed, I would be happy to try to setup a bot for some of the
Windows builds, because they also tend to be easy to break.
However, I am not sure if it will be easy to get a stable Windows VM with
licences (MSVC or MingW windows would be best, but if not possible, maybe cross
compile from Linux MingW -- if it works -- could still be a good first step).
On 13 March 2014 01:27, Greg Clayton <[email protected]> wrote:
Most plug-ins should be built on all systems all the time. The _only_ plugins
that shouldn't be built are ones that can only build on the native system and
only make sense to use on the native system. That means "ProcessLinux" is for
linux only, and "ProcessFreeBSD" is for FreeBSD only. Right now there are a
bunch of Apple plug-ins that aren't being built for everyone, but they should
be and Todd Fiala and I are working on making sure they are included soon.
So the answer is "make the build work" for all plug-ins. Right now we have 3
build systems: Xcode (darwin only), make and cmake. Usually when changes get
made things break so we need to fix them.
Greg
On Mar 12, 2014, at 8:22 AM, Kuba Ober <[email protected]> wrote:
> Currently, the build scripts and source/lldb.cpp disagree on what plugins are
> included for Darwin.
>
> The build scripts don’t build the JITLoaderGDB and ProcessElfCore, yet
> lldb.cpp
> tries to initialize and terminate those plugins, resulting in link failure.
>
> What’s the right way to go? Should I patch to disable those plugins, or to
> enable them?
>
> Cheers, Kuba Ober
> _______________________________________________
> lldb-dev mailing list
> [email protected]
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
