Tad Fisher

It's dead code at this point. I can put some effort into porting the maintained version from my work's internal codebase. It requires Gradle hacks to actually use it in...

Yeah, this is kind of a dilemma, because it can be useful to use cmdline-tools with non-Nix-managed SDKs and JDKs. Maybe exposing a `passthru.unwrapped` derivation could serve that use case,...

No, this isn't expected, and it sucks that the Android SDK repositories allow mutating artifacts like that. I'll keep an eye out for more breakage like this.

Note that nothing in a patent is enforceable except for the **Claims** section at the bottom. Everything else is fluff or explanatory, but only the claims comprise the actual patent.

Would it not be a better option (in the long run) to get the `mxsfb-drm` driver running? That would give us a more modern driver to build upon, and more...

Thanks for testing! I was able to build this with the following flake: ```nix { inputs = { gradle2nix.url = "github:tadfisher/gradle2nix/v2"; }; outputs = { self, gradle2nix }: { packages.x86_64-linux.default...

D'oh! The command should be `nix run github:tadfisher/gradle2nix/v2 -- -t build -- -x test`.

Hmm, `createExe` isn't going to work unless you're on a Windows system. Does `./gradlew build -x test` work when you check out the repo?

Another thing I just thought of is that I have `nix-ld` installed on my system, so I'm wondering if that leaks into the nix sandbox. This would be really important...

Yeah, so the problem isn't gradle2nix per se, it's that `launchj` runs a binary that links against system libraries. This is unfortunate but could be hacked around. First step for...