Find all dependencies using pkg-config #301
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#301
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have some dependencies we find via
CMake, which requires this sort of support code in nixpkgs: https://github.com/NixOS/nixpkgs/pull/310453.To avoid this, we could spare some time fixing dependencies who are not compatible with
pkg-config.note: boost does not provide a pkg-config, but is an exception to this, as Meson does not use CMake to find boost (though its logic is broken under Nix, see https://github.com/NixOS/nixpkgs/issues/86131, which we have a workaround for in package.nix)
pegtl does not provide pkg-config files eiher, unless we vendor that this will be impossible to resolve
@pennae wrote in #301 (comment):
i think this would be reasonable to patch in nixpkgs though.
dunno about that, seems like a really weird thing to do? if anything that should be patched in the projects themselves, not in their packaging
I think among all the things we have to do, this is probably quite low priority. The support code is annoying but not a massive maintenance churn once figured out.
It is probably a good task to give to someone new who wants to get started with build systems code though.