-
-
Notifications
You must be signed in to change notification settings - Fork 16.7k
Open
Labels
6.topic: architectureRelating to code and API architecture of NixpkgsRelating to code and API architecture of Nixpkgs6.topic: cross-compilationBuilding packages on a different platform than they will be used onBuilding packages on a different platform than they will be used on6.topic: muslRunning or building packages with musl libcRunning or building packages with musl libc6.topic: staticStatic builds (e.g. pkgsStatic)Static builds (e.g. pkgsStatic)
Description
Issue description
For my work on static-haskell-nix I need an overlay that has both .so
files and .a
files.
This is because I need .a
s for linking Haskell exes statically, but .so
files for executing TemplateHaskell.
Right now pkgsStatic
not only adds .a
files, but also disables .so
files:
makeStaticBinaries
andmakeStaticLibraries
set--disable-shared
static.nix
uses thosestatic.nix
disables shared Haskell libs that TH needs
Proposal
I think we should have the following stack of overlays:
pkgsMusl <- pkgsStatic <- pkgsStaticOnly
pkgsMusl
is what it is now: All packages using musl libcpkgsStatic
should be the one that has.a
files added to all libraries (in addition to.so
files), and all binaries (including Haskell ones) linked statically where possiblepkgsStaticOnly
should be whatpkgsStatic
is now: Having only static libraries and binaries, getting rid of.so
files.
cdepillabout, bb010g, NorfairKing, anka-213, expipiplus1 and 10 moreAleXoundOS and ScottFreeCode
Metadata
Metadata
Assignees
Labels
6.topic: architectureRelating to code and API architecture of NixpkgsRelating to code and API architecture of Nixpkgs6.topic: cross-compilationBuilding packages on a different platform than they will be used onBuilding packages on a different platform than they will be used on6.topic: muslRunning or building packages with musl libcRunning or building packages with musl libc6.topic: staticStatic builds (e.g. pkgsStatic)Static builds (e.g. pkgsStatic)