Date: Mon, 27 Jul 2009 14:58:25 -0700 From: Xin LI <delphij@delphij.net> To: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= <gabor@kovesdan.org> Cc: hackers@FreeBSD.org Subject: Re: bsd.lib.mk question Message-ID: <4A6E2301.8080308@delphij.net> In-Reply-To: <4A6C1508.7020309@kovesdan.org> References: <4A6C1508.7020309@kovesdan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Gábor Kövesdán wrote: > Hi, > > I wonder if there's a conventional way of building _only_ shared > libraries using bsd.lib.mk. At default, it builds static, shared and > profiled libraries, which is a waste of time because I only need shared > libraries, which I use as on-demand loadable modules. Adjusting _LIBS > after the inclusion of bsd.lib.mk doesn't help and there are no knobs to > control the behaviour. What should I do? If you define LIB= (or, not define it at all), and define both SHLIB and SHLIB_MAJOR, then only shared library is being built and installed. Example: LIB= SHLIB= test SHLIB_MAJOR= 0 Would build libtest.so.0, but no libtest.a nor libtest_p.a. Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpuIwEACgkQi+vbBBjt66C50gCgul420W4siZi3VBA2ZnHxNz4J UesAoMIoSzqF0rE6TzvZ5/D0vyjbTc71 =Y5xW -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A6E2301.8080308>