From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 28 Jul 2015 01:37:12 -0700 (PDT) From: Juan RP To: voidlinux , master...@googlemail.com Cc: master...@googlemail.com Message-Id: In-Reply-To: <46e041ef-6c62-49c3-bb21-d8c96f3fb778@googlegroups.com> References: <46e041ef-6c62-49c3-bb21-d8c96f3fb778@googlegroups.com> Subject: Re: Statically compile libraries into packages MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1982_1353278367.1438072632378" ------=_Part_1982_1353278367.1438072632378 Content-Type: multipart/alternative; boundary="----=_Part_1983_877792026.1438072632378" ------=_Part_1983_877792026.1438072632378 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This really depends if the software build system is prepared for static builds, but in 75% of packages you can accomplish this by setting CFLAGS and LDFLAGS like so: $ printf 'CFLAGS="-static"\nLDFLAGS="-static"\n' >> srcpkgs/grep/template If you want to make this permanent it would be better if you conditionalize those settings in a `static` build option, as has been done already in some packages. ------=_Part_1983_877792026.1438072632378 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
This really depends if the software build system is prepared for static builds, but in 75% of
packages you can accomplish this by setting CFLAGS and LDFLAGS like so:

$ printf 'CFLAGS="-static"\nLDFLAGS="-static"\n' >> srcpkgs/grep/template

If you want to make this permanent it would be better if you conditionalize those settings
in a `static` build option, as has been done already in some packages.
------=_Part_1983_877792026.1438072632378-- ------=_Part_1982_1353278367.1438072632378--