@Ericson2314 this looks like it will be breaking cross: https://mesonbuild.com/Release-notes-for-0-55-0.html#config-tool-based-dependencies-no-longer-search-path-for-cross-compiling

@jtojnar true. There might be environmental variables for some of them, though.

status?

I am not sure about the extent of the breakage. Could we make a hydra jobset for this branch running release-cross.nix? Or do we just merge this to staging and hope for the best?

I would just merge and hope for the best. We can make the cross file unconditionally contain stuff like

qmake = '${stdenv.cc.hostPrefix}qmake'

which I think will work.

Here is the commit in question: mesonbuild/meson@245d659

Here is the list of known dependencies: https://github.com/mesonbuild/meson/blob/24227a95531b21a04bf2514a5b8f61ae29d47043/mesonbuild/dependencies/__init__.py#L41-L89

We care about those that use/extend ConfigToolDependency class, which is quite a few. Maybe we could find all *-config programs on PATH and add them to cross file.

because config-tools are such a pain, I bet we're having trouble with many of them anyways, so I would deal with it on an as-needed basis.

Merging then.

Just ping me liberally if things do fail! :)