
Because we're using plain buildtype these have to be passed manually. See: https://gitlab.gnome.org/GNOME/gtk/blob/3.24.10/meson.build#L59 With autotools the mapping for the the options to the defines was: yes: G_ENABLE_DEBUG G_ENABLE_CONSISTENCY_CHECKS minimum: G_ENABLE_DEBUG G_DISABLE_CAST_CHECKS no: G_DISABLE_CAST_CHECKS G_DISABLE_ASSERT G_DISABLE_CHECKS So we're passing the exact ones that would've been used for minimum. Additionally it isn't a good idea to pass the equivalents used for "no" as it eliminates G_ENABLE_DEBUG which disables pre-condition checks and assertions. The actual option only existed to serve people who needed a specific build of GTK for very specific environments. And now they are much better served with meson's plain buildtype and figuring out what to pass themselves.
Nixpkgs is a collection of packages for the Nix package manager. It is periodically built and tested by the Hydra build daemon as so-called channels. To get channel information via git, add nixpkgs-channels as a remote:
% git remote add channels https://github.com/NixOS/nixpkgs-channels.git
For stability and maximum binary package support, it is recommended to maintain
custom changes on top of one of the channels, e.g. nixos-19.03
for the latest
release and nixos-unstable
for the latest successful build of master:
% git remote update channels
% git rebase channels/nixos-19.03
For pull requests, please rebase onto nixpkgs master
.
NixOS Linux distribution source code is located inside
nixos/
folder.
- NixOS installation instructions
- Documentation (Nix Expression Language chapter)
- Manual (How to write packages for Nix)
- Manual (NixOS)
- Community maintained wiki
- Continuous package builds for unstable/master
- Continuous package builds for 19.03 release
- Tests for unstable/master
- Tests for 19.03 release
Communication:
Note: MIT license does not apply to the packages built by Nixpkgs, merely to the package descriptions (Nix expressions, build scripts, and so on). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.