Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
building-packages [2015/05/07 00:54] – snacsnocbuilding-packages [2022/12/19 05:06] (current) – snacsnoc
Line 1: Line 1:
 ====== Building packages ====== ====== Building packages ======
  
-For native compilations export CC to ''CC="musl-gcc -static"'' and compile normally. See below for an example.+Example build flow:
  
 <code> <code>
-export CC="musl-gcc -static"+export LDFLAGS="-s"
 export C_INCLUDE_PATH=/include:/usr/include export C_INCLUDE_PATH=/include:/usr/include
 +
  
 tar xvf myfancysoftware-1.0.tar.gz && cd myfancysoftware-1.0 tar xvf myfancysoftware-1.0.tar.gz && cd myfancysoftware-1.0
Line 16: Line 17:
 </code> </code>
  
 +If configure complains about /lib/cpp failing sanity check, try this:
 +
 +<code>
 +fbpkg install ucpp
 +ln -sf /usr/bin/ucpp /lib/cpp
 +export CPPFLAGS="-I/include -I/usr/include"
 +</code>
 +and recompile.
 +
 +**pkg-config**
 +
 +Use pkgconf as a drop-in replacement instead, install via fbpkg
 +<code>
 +ln -sf /usr/bin/pkgconf /usr/bin/pkg-config
 +</code>
  
 +**Notes**
  
 For non-native compilations (using the musl toolchain) set ''--host=i486-musl-linux'' and enable any static compilation options (such as CFLAGS="static").  For non-native compilations (using the musl toolchain) set ''--host=i486-musl-linux'' and enable any static compilation options (such as CFLAGS="static"). 
Line 22: Line 39:
 As well, for either types of builds setting ''CFLAGS="-s" LDFLAGS="-s"'' is a good idea to automatically have gcc to strip the libs and binaries. As well, for either types of builds setting ''CFLAGS="-s" LDFLAGS="-s"'' is a good idea to automatically have gcc to strip the libs and binaries.
  
-A mirror of all the packages tars are available here: http://snacklinux.org/tars/+A mirror of all the packages tars are available here: http://snacklinux.geekness.eu/tars/