Statically compile libraries into packages

Statically compile libraries into packages

[Stefan Mühlinghaus]

[-- Attachment #1.1: Type: text/plain, Size: 355 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 400 bytes --]

Re: Statically compile libraries into packages

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 406 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 480 bytes --]

Re: Statically compile libraries into packages

[Stefan Mühlinghaus]

[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]

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 :) 

[-- Attachment #1.2: Type: text/html, Size: 1025 bytes --]