| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |\ \ \ \
| | |_|_|/
| |/| | | |
`lib.fileset.fromSource`: init
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\| | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Minor `lib.fileset` cleanups
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Thanks nixd!
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Just minor changes like:
- Always using "X is a Y, but it should be Z"
- "X is a path that does not exist" rather than "X does not exist"
- Always using multi-line strings for errors
- Always quoting string-like values and not quoting path-like values
- But do quote filesystem roots. Even though they're paths, they might
be very small, good to have quotes to know the start/end
- Capitalise the first word
- Distinguish root vs filesystem root more
|
| | | | |_|/
| | |/| |
| | | | |
| | | | | |
This problem was fixed in https://github.com/nix-community/nixdoc/pull/81 which is included in version 2.5.1, which is now used in Nixpkgs
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Along the lines of `assertOneOf`, but expects a list of values to be
compared. This gives a good error message and is useful for lists of
values, like `supportedGhcVersions` in the arguments of
`haskell-language-server`.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need this stuff to be available in lib so make-derivation.nix can
access it to construct the Meson cross file.
This has a couple of other advantages:
- It makes Rust less special. Now figuring out what Rust calls a
platform is the same as figuring out what Linux or QEMU call it.
- We can unify the schema used to define Rust targets, and the schema
used to access those values later. Just like you can set "config"
or "system" in a platform definition, and then access those same
keys on the elaborated platform, you can now set "rustcTarget" in
your crossSystem, and then access "stdenv.hostPlatform.rustcTarget"
in your code.
"rustcTarget", "rustcTargetSpec", "cargoShortTarget", and
"cargoEnvVarTarget" have the "rustc" and "cargo" prefixes because
these are not exposed to code by the compiler, and are not
standardized. The arch/os/etc. variables are all named to match the
forms in the Rust target spec JSON.
The new rust.target-family only takes a list, since we don't need to
worry about backwards compatibility when that name is used.
The old APIs are all still functional with no warning for now, so that
it's possible for external code to use a single API on both 23.05 and
23.11. We can introduce the warnings once 23.05 is EOL, and make them
hard errors when 23.11 is EOL.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
lib.strings: add `replicate`
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
`strings.replicate` returns n copies of a string, concatenated into a new
string
Co-authored-by: Silvan Mosberger <github@infinisil.com>
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | | |
I didn't add these arguments, so these comments are from my understading of the arguments.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have several cross-compilation bugs that show up if
hostPlatform!=buildPlatform yet
hostPlatform.config==buildPlatform.config.
These bugs have appeared and disappeared as we've fiddled with the
definition of equality for platform objects. This commit adds a
clear-cut case where they are *not* equal and never will be, so we
can test it.
|
| |\ \ \ \
| | | | |
| | | | | |
lib.fileset: Add an additional argument in the design docs
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
lib.filesystem: Don't test Nix-specific error messages
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In https://github.com/NixOS/nix/pull/9269 the error messages change
which would've broken this test.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
`lib.fileset.difference`: init
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | | |
Corrects a minor typo in the description of `fix`; namely that `fix` allows factoring out syntactic recursion from another function.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
lib.getExe': check arguments
|
| | | | | | | |
|
| | | |_|/ /
| |/| | | |
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | | |
`lib.fileset.toSource`: Improve error for unknown file types
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Compared to the parent commit, this removes any detectable performance
cost :)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This does decrease performance unfortunately
Benchmarking expression toSource { root = ./.; fileset = ./.; }
Mean CPU time 0.103747 (σ = 0.012415) for 10 runs is 97.32181384964636% (σ = 16.34179537413021%) of the old value 0.106602 (σ = 0.0125571)
Statistic .envs.elements (205920) is 105.5842% (+10891) of the old value 195029
Statistic .gc.totalBytes (20247696) is 101.7495% (+348160) of the old value 19899536
Statistic .nrThunks (134824) is 108.7878% (+10891) of the old value 123933
Statistic .symbols.number (996) is 100.1005% (+1) of the old value 995
Statistic .values.number (275238) is 104.1199% (+10891) of the old value 264347
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently just throws the Nix error because unknown file types are not
supported by the Nix store, but nothing catches this error earlier (yet,
see next commit)
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| |/ / /
|/| | | |
lib/systems/parse.nix: add removeAbiSuffix, use it
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
gnu-config will ignore the portion of a triple matching the regex
`e?abi.*$` when determining the validity of a triple. In other
words, `i386-linuxabichickenlips` is a valid triple.
This commit updates our parsing routines to match gnu-config.
I was recently surprised to discover that it is in fact possible to
shoehorn ABI flavors into nix doubles in a way which preserves their
property of being a (non-canonical) subset of the valid gnu-config
triples. This commit is required in order to exploit that discovery
to add automatic detection of ILP32 platforms (64-bit void*, 32-bit
int, like the Apple Watch and MIPS n32) to Nix.
|
| |\ \ \
| | | |
| | | | |
`lib.fileset.fileFilter`: init
|
| | |/ / |
|
| | | |
| | |
| | |
| | | |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |/ /
| |
| |
| |
| |
| | |
Add the "Type:" blocks.
Move the examples below the descriptions whenever possibles
Add "Example:" tags before the examples moved below the descriptions.
|
| |\ \
| | |
| | | |
lib/options: mkPackageOption: document better, add pkgsText and usePname options, refactor
|
| | | | |
|
| | | |
| | |
| | |
| | | |
mkPackageOption
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|