Re: Why not provide libclang.so in base?
--NY6JkbSqL3W9mApi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jul 19, 2012 at 09:31:04AM +0200, Dimitry Andric wrote:
> On 2012-07-18 14:54, Yanhui Shen wrote:
> > I'm using clang-complete plugin in vim,
> > it claims with libclang.so instead of bin/clang it works better.
> >=20
> > However libclang.so is not installed by a default "make buildworld && m=
ake
> > installworld",
> > even with 'WITH_CLANG_EXTRAS=3D"YES"' in src.conf.
>=20
> This is because it would add quite a lot of build overhead to produce
> that .so file: all the object files will need to be recompiled yet again
> for shared library support.
>=20
> That said, we will probably want to provide at least a shared LLVM lib
> in the future, since it can be re-used by other programs. When that
> happens, it would not be too much extra work to provide a shared Clang
> library.
When I talked to Chris Lattner about shared libraries, his advice was
that under no circumstances should we consider supporting any C++ APIs
=66rom the base system. We can link tools in the system with them and we
can provide supportable C API wrappers as Apple does, but any port that
links against a libclang.so or libLLVM.so is doomed to break so ports
should link against port versions so they can be updated as needed.
-- Brooks
--NY6JkbSqL3W9mApi
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iD8DBQFQEWHnXY6L6fI4GtQRAjn8AKDMSMHPgImpcmwE7toZsk2DONQMVACfSt4G
gofC1BxsVUvw6yQnkoqhhAA=
=rze4
-----END PGP SIGNATURE-----
--NY6JkbSqL3W9mApi--
討論串 (同標題文章)
完整討論串 (本文為第 3 之 3 篇)：