Expose a function to build a single Emacs Lisp package #178
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
akirak
force-pushed
the
expose-build-function
branch
from
193d493 to
2981ad0
Compare
|
Thank you, this is still relevant to me, I will check if I can replace trivialBuild with this one. |
This function produces a derivation that follows certain conventions. Source files will be built and installed to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR officially (though the library API may be changed in the future) exposes the function for building a single Emacs Lisp package, from the
libentry point of the flake.The function should take two arguments:
pkgs, i.e.nixpkgs.legacyPackages.${system}, and an attribute value frompackageInputsin the config.@terlar I am not sure if you still need this, but is it supposed to fix #65?