| 15 Jul 2021 |
piegames | Instead of libc = "newlib";, i need to use libnano. Is this generally possible in nixpkgs? | 12:26:50 |
sterni (he/him) | libnano is not packaged so no | 12:27:29 |
sterni (he/him) | but it is not impossible in general :) | 12:27:37 |
| 17 Jul 2021 |
symphorien | this PR is probably worth mentionning here: https://github.com/NixOS/nixpkgs/issues/130349 | 14:01:52 |
siraben (he/him) | That seems like a good idea, it's recurring pattern in Nixpkgs and I sometimes have to second-guess what to compare. | 15:27:02 |
symphorien | It used to exist and was removed so I'd like yo hear why 😃 | 15:57:42 |
symphorien | I think there was stdenv.isCross | 17:23:11 |
Rick (Mindavi) | In reply to @symphorien:xlumurb.eu It used to exist and was removed so I'd like yo hear why 😃 John has a good point | 17:24:49 |
symphorien | Oh that's the reason | 17:27:00 |
Rick (Mindavi) | In short: there's no one-size-fits-all solution, and being explicit is better | 17:41:14 |
sterni (he/him) | sometimes you'd need to check targetPlatform equality for example | 20:53:55 |
sterni (he/him) | also x86_64 -> i686 is still cross compiling, but you could e. g. run tests | 20:54:18 |
sterni (he/him) | so yeah one size does not fit all | 20:54:30 |
| 18 Jul 2021 |
| philipp joined the room. | 20:25:13 |
philipp | Can somebody explain to me where the non 32 bit version of the mingw headers are? One would assume it's pkgsCross.mingwW64.windows.mingw_w64_headers but that evalutes to /nix/store/m7mvg8ldx7fj0rliz60gjyrzy7rm6ig2-mingw-w64-x86_64-w64-mingw32-6.0.0-headers and throws an #error Only Win32 target is supported! error. | 20:27:15 |
philipp | Package for reference:
{ stdenv, lib, fetchFromGitHub, glslang, meson, ninja, wine, pkgsCross }:
stdenv.mkDerivation rec {
pname = "dxvk-installer";
version = "1.9";
src = fetchFromGitHub {
owner = "doitsujin";
repo = "dxvk";
rev = "v${version}";
sha256 = "01db23ncbrrq0cqnp25fg5plp88v5i5ri0i38m0wida8mw3mmjsa";
};
mesonFlags = [ "--cross-file build-win64.txt" "--buildtype release" ];
nativeBuildInputs = [
glslang
meson
ninja
pkgsCross.mingwW64.buildPackages.gcc
pkgsCross.mingwW64.windows.mingw_w64
pkgsCross.mingwW64.windows.mingw_w64_headers
wine
];
}
| 20:27:52 |
philipp | * Package for reference:
{ stdenv, lib, fetchFromGitHub, glslang, meson, ninja, wine, pkgsCross }:
stdenv.mkDerivation rec {
pname = "dxvk-installer";
version = "1.9";
src = fetchFromGitHub {
owner = "doitsujin";
repo = "dxvk";
rev = "v${version}";
sha256 = "01db23ncbrrq0cqnp25fg5plp88v5i5ri0i38m0wida8mw3mmjsa";
};
mesonFlags = [ "--cross-file build-win64.txt" "--buildtype release" ];
nativeBuildInputs = [
glslang
meson
ninja
pkgsCross.mingwW64.buildPackages.gcc
pkgsCross.mingwW64.windows.mingw_w64_headers
wine
];
}
| 20:52:35 |
| 19 Jul 2021 |
symphorien | You need to take all your packages from pkgCross.ming.... | 05:29:30 |
symphorien | The easiest way is to take callPackage from it like in https://nixos.wiki/wiki/Cross_Compiling | 05:31:46 |
philipp | thx, will look into that. | 08:18:33 |
philipp | I ended up with
{ stdenv, lib, fetchFromGitHub, glslang, meson, ninja, pkgsCross, gcc, buildPackages }:
stdenv.mkDerivation rec {
pname = "dxvk-installer";
version = "1.9";
src = fetchFromGitHub {
owner = "doitsujin";
repo = "dxvk";
rev = "v${version}";
sha256 = "01db23ncbrrq0cqnp25fg5plp88v5i5ri0i38m0wida8mw3mmjsa";
};
mesonFlags = [ "--cross-file build-win64.txt" "--buildtype release" ];
depsBuildBuild = [ buildPackages.stdenv.cc buildPackages.meson buildPackages.ninja ];
depsBuildTarget = [
pkgsCross.mingwW64.windows.mingw_w64_headers
glslang
buildPackages.gcc
];
}
called via nix-build -E 'with import <nixpkgs> {}; pkgsCross.mingwW64.callPackage ./dxvk.nix { }' but I still end up with the same error. Do I have to get mingwW64 from somewhere else now? I can't find it.
| 15:00:17 |
philipp | Redacted or Malformed Event | 22:23:14 |
philipp | Redacted or Malformed Event | 22:23:27 |
| 20 Jul 2021 |
symphorien | Don't use pkgCross at all in the callPackaged file | 06:03:28 |
symphorien | Instead of depsBuildTarget it's probably buildInputs ie depsBuildHost | 06:03:39 |
symphorien | Hmmm I have a doubt, I'm not used to the rigorous names | 06:15:44 |
philipp | When I don't use pkgsCross, how do I get the mingw_w64_headers then? They only live in the crossPackages afaik. | 10:09:38 |
symphorien | It's magic and called splicing: you get a different one depending on whether you use it in buildInputs or nativeBuildInputs | 10:26:08 |
philipp | Ah, turns out I conflated general cross compiling issues with issues stemming from the mingw64 version in nixpkgs being pretty old. | 15:57:19 |
| 22 Jul 2021 |
siraben (he/him) | philipp: the mingw versions were updated recently | 13:01:55 |