Right, that's exactly my thinking too. Hence my suggestion in the previous post (which I suspect we just crossed paths on the email, so you didn't see it yet) to make jsut an LLDB_HOST_BSD that covers all of them. Because we probably need OpenBSD too in most cases, and exceptions should be rare.
On Fri, Sep 12, 2014 at 10:29 AM, Ed Maste <ema...@freebsd.org> wrote: > On 12 September 2014 12:57, Zachary Turner <ztur...@google.com> wrote: > > What are the differences between FreeBSD and NetBSD? Every time we check > > for one, should we also be checking for the other? > > I suspect though that where __FreeBSD__ is used in combination with > another OS (e.g. __FreeBSD__ || __linux__, or __FreeBSD__ || > __APPLE__), we likely need __NetBSD__ there too. > > Keep in mind though that the NetBSD support so far is really just > basics to get the debugger to build and run, but AFAIK there's none of > the kernel debugging interface side at all yet. I expect there will > be a reasonable amount shared between FreeBSD and NetBSD there, but a > lot that's OS-specific too. >
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
