Date: Tue, 16 Dec 2014 15:58:39 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Ed Maste <emaste@freebsd.org> Cc: freebsd-toolchain@freebsd.org Subject: Re: Migration to dynamic libs for llvm and clang Message-ID: <41F09A1C-01D6-42C9-B495-244DFC2B0364@FreeBSD.org> In-Reply-To: <CAPyFy2DeLiFAW_yS14r1n89r92MFG1sbX88rNgaJshwH9-%2BkQg@mail.gmail.com> References: <CAPyFy2DeLiFAW_yS14r1n89r92MFG1sbX88rNgaJshwH9-%2BkQg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ed, Please can we have a name other than libclang, to avoid name collisions = and confusion with, uh, libclang? libcfe maybe? David On 16 Dec 2014, at 15:46, Ed Maste <emaste@freebsd.org> wrote: > One of goals for the toolchain prior to the FreeBSD 11 branch is to > create a libllvm.so and libclang.so for use by all of the LLVM family > tools installed in the base system. This message is just a heads-up in > case anyone has questions or comments on the idea. >=20 > We currently build a large number of static libs for the llvm and > clang components, which are reused in a number of tools in the LLVM > family. The resulting binaries end up quite large, and as a group > require a lot of disk space. For example, LLDB includes a copy of > Clang, used as its expression parser. As a result, on my desktop > /usr/bin/clang and /usr/bin/lldb are both 27MB. >=20 > Over time we may add additional LLVM family tools (e.g., > llvm-objdump), and this will help avoid excessive bloat as we do so. >=20 > I expect libllvm.so and libclang.so will go in /usr/lib/private. > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to = "freebsd-toolchain-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41F09A1C-01D6-42C9-B495-244DFC2B0364>