I will move this over to staging once I fixed some stuff.

@LnL7 We will have the same issue with Darwin frameworks here as in #83099
Should I explicitly add the darwin services as a buildInput to buildGoPackage?

(N.B. In the other, I say go with depsTargetTargetPropagated)

I may not have yet understand very well the purpose of strictDeps and how it works. Is it well documented somewhere? Maybe in a blog article, or in a topic in the forum?

Why in the case of dde-api, dde-daemon, and startdde, some build dependencies needs to migrate from nativeBuildInputs to buildInputs when strictDeps is true?

@romildo There is some documentation, though not enough, in https://nixos.org/nixpkgs/manual/#chap-cross . Basically, strictDeps makes native act like cross always does, rigorously treating the various sorts of dependencies differently (e.g. run-time deps don't go on the PATH at build time, -L and -isystem flags stay separate, etc., etc).

By not having native be more permissive than cross, we make the cross builds much less likely to bitrot.

@GrahamcOfBorg build dnscrypt-proxy2

Cherry-picked to ff2ea91 in staging