From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 28 Jul 2015 08:58:32 -0700 (PDT) From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= To: voidlinux Cc: master...@googlemail.com Message-Id: <3b3f6291-bced-4641-a151-243bdbc0bbfa@googlegroups.com> 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_273_567462479.1438099112990" ------=_Part_273_567462479.1438099112990 Content-Type: multipart/alternative; boundary="----=_Part_274_1902244989.1438099112990" ------=_Part_274_1902244989.1438099112990 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What I'm trying to achieve is build a package for program X that depends on library Y. Making another package for Y is not feasible because in this particular case X needs a very specific and/or outdated version of Y. So I want to construct the package template for X in such a way that it downloads and builds both distfiles for X and Y and then statically links them together so that the target system is not cluttered with library garbage. I'm pretty sure I can make that work by copying files around in the working directory and patching the Makefile of X. It would be somewhat more elegant if I could "install" the statically compiled library of Y and its header-files to some temporary lib/include directory on the building system which would automatically be used when compiling X and afterwards cleaned. I of course realize that this is a somewhat esoteric use-case but I thought I'd better ask before doing it manually :) ------=_Part_274_1902244989.1438099112990 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
What I'm trying to achieve is build a package for prog= ram X that depends on library Y. Making another package for Y is not feasib= le because in this particular case X needs a very specific and/or outdated = version of Y. So I want to construct the package template for X in such a w= ay that it downloads and builds both distfiles for X and Y and then statica= lly links them together so that the target system is not cluttered with lib= rary garbage.

I'm pretty sure I can make that work b= y copying files around in the working directory and patching the Makefile o= f X. It would be somewhat more elegant if I could "install" the s= tatically compiled library of Y and its header-files to some temporary lib/= include directory on the building system which would automatically be used = when compiling X and afterwards cleaned.

I of cour= se realize that this is a somewhat esoteric use-case but I thought I'd = better ask before doing it manually :)=C2=A0
------=_Part_274_1902244989.1438099112990-- ------=_Part_273_567462479.1438099112990--