From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 28 Jul 2015 01:28:52 -0700 (PDT)
From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= <master...@googlemail.com>
To: voidlinux <void...@googlegroups.com>
Message-Id: <46e041ef-6c62-49c3-bb21-d8c96f3fb778@googlegroups.com>
Subject: Statically compile libraries into packages
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_3787_80649635.1438072132069"

------=_Part_3787_80649635.1438072132069
Content-Type: multipart/alternative; 
	boundary="----=_Part_3788_23530112.1438072132070"

------=_Part_3788_23530112.1438072132070
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Is there an intended way to statically compile a library into a package?

I'd usually compile the library first, copy the resulting .a and header 
files over to the actual programs sources, maybe adapt the makefile a 
little and then compile it. This seems somewhat unelegant and I wonder if 
maybe xbps-src has some mechanism to aid with this situation.

------=_Part_3788_23530112.1438072132070
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<div dir="ltr">Is there an intended way to statically compile a library into a package?<div><br></div><div>I&#39;d usually compile the library first, copy the resulting .a and header files over to the actual programs sources, maybe adapt the makefile a little and then compile it. This seems somewhat unelegant and I wonder if maybe xbps-src has some mechanism to aid with this situation.</div></div>
------=_Part_3788_23530112.1438072132070--

------=_Part_3787_80649635.1438072132069--