Stop using nix to build lix-doc #256
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#256
Loading…
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 meson, let's make our rust stuff not make our downstreams cry unnecessarily if possible.
note: this may be blocked on meson being bad.
from lily:
this exists and is best described as a joke until someone writes code generation tooling for this stuff: https://coaxion.net/blog/2023/04/building-a-gstreamer-plugin-in-rust-with-meson-instead-of-cargo/
it's also possible to use cargo with meson, but that is also painful and may suck for downstreams anyway due to cargo vendoring. jade sighs
We plan on making Lix reasonable to build without Nix in general. We will make this work, at some point
This issue was mentioned on Gerrit on the following CLs:
This turned out to be a lot easier than we expected! Most of the difficulty was from Meson's docs being bad