Date: Tue, 16 Dec 2014 17:04:06 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: David Chisnall <theraven@FreeBSD.org> Cc: freebsd-toolchain@freebsd.org Subject: Re: Migration to dynamic libs for llvm and clang Message-ID: <D359161D-B14C-4F19-8F0D-57FE530D0AF4@FreeBSD.org> In-Reply-To: <41F09A1C-01D6-42C9-B495-244DFC2B0364@FreeBSD.org> References: <CAPyFy2DeLiFAW_yS14r1n89r92MFG1sbX88rNgaJshwH9-%2BkQg@mail.gmail.com> <41F09A1C-01D6-42C9-B495-244DFC2B0364@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_5C008411-5CEB-4152-A2A4-0B24335EFDC1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16 Dec 2014, at 16:58, David Chisnall <theraven@FreeBSD.org> wrote: > 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. > Hi Ed, >=20 > Please can we have a name other than libclang, to avoid name = collisions and confusion with, uh, libclang? libcfe maybe? This is precisely why the libs should go into /usr/lib/private, so as to avoid collisions with any upstream libraries installed by e.g. ports (or when you manually run "make install" after building). I'm not sure we want to go the 'libbsdfoo.so' route again, as Baptiste tried this before, and seems to have reversed it again. :) That said, I agree with the general idea, but one of the first things we should decide is whether this will be optional or not. Having to maintain yet another WITH_CLANG_FOO option is burdensome... -Dimitry --Apple-Mail=_5C008411-5CEB-4152-A2A4-0B24335EFDC1 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlSQV/oACgkQsF6jCi4glqMVtQCgj7NSJe6VwmTHdGDWQW7qqUfY hSkAn1B6K8m9DrhECRHKXVsfWqgTqAM1 =NUpV -----END PGP SIGNATURE----- --Apple-Mail=_5C008411-5CEB-4152-A2A4-0B24335EFDC1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D359161D-B14C-4F19-8F0D-57FE530D0AF4>