!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

586 Members
Rust129 Servers

Load older messages


SenderMessageTime
6 Jul 2025
@andrew15_5:matrix.orgAndrew3 things.jpg
Download 3 things.jpg
18:00:10
@andrew15_5:matrix.orgAndrewI assume the CLI binary both, adds the Runtime to PWD and launches the GUI.18:00:42
@andrew15_5:matrix.orgAndrewReally didn't expect a second window to appear when the app launches.18:01:18
@andrew15_5:matrix.orgAndrewIt also takes maybe like 30 seconds to copy about 11 MiB of runtime data before the app can actually show up. But after that it launches in one or two seconds.18:01:56
@andrew15_5:matrix.orgAndrewOverall, success. But at what cost...18:02:16
@andrew15_5:matrix.orgAndrewI thought a bit about it, and I think you can't really build any GUI cross-platform/from-Linux app and run it as is on any Windows system.18:03:28
@andrew15_5:matrix.orgAndrewLike for Python you'd have to install Python. Though you can technically bundle everything into a single binary. Not user if it works with GUI apps that use Qt or whatever.18:04:22
@andrew15_5:matrix.orgAndrewPerhaps same problems will arise with C++ apps.18:04:56
@andrew15_5:matrix.orgAndrewSo you kinda have to build natively...18:05:19
@andrew15_5:matrix.orgAndrewAlthough Dioxus Blitz supposedly can be statically linked, since it renders natively. But I haven't looked into this.18:06:23
@andrew15_5:matrix.orgAndrew Maybe https://github.com/rust-cross/cargo-xwin can just work. Though no Nix and no native dx support. 18:55:20
7 Jul 2025
@charles:computer.surgeryCharlescargo-llvm-cov added a git dev-dependency in its latest release that isn't reflected in Cargo.lock on crates.io, breaking nixpkgs' "download the lockfile from crates.io and build against that to avoid checking the entire lockfile into nixpkgs" workflow: https://github.com/taiki-e/cargo-llvm-cov/commit/fb528c913f5b5577b6971dae9d99d70babdd42e006:49:53
@charles:computer.surgeryCharleshow should i deal with this06:49:59
@charles:computer.surgeryCharles

i can think of two options:

  1. bug the maintainer to make a new release that fixes the crates.io lockfile (crates.io allows git dependencies in dev-dependencies)
  2. something else
06:50:35
@charles:computer.surgeryCharlesi feel like at this point i would prefer "something else" but i'm not sure what that should/could be06:51:42
@charles:computer.surgeryCharlessince it seems like repeatable builds are really not a priority for this maintainer06:51:56
@charles:computer.surgeryCharles * cargo-llvm-cov added a git dev-dependency in its latest release that isn't reflected in Cargo.lock on crates.io, breaking nixpkgs' "download the lockfile from crates.io and build against that to avoid checking the entire lockfile into nixpkgs" workflow: https://github.com/taiki-e/cargo-llvm-cov/commit/fb528c913f5b5577b6971dae9d99d70babdd42e0 06:52:51
@charles:computer.surgeryCharles

i guess checking in cargo.lock isn't that uncommon:

$ fd 'Cargo\.lock' | wc -l
110
06:55:59
@charles:computer.surgeryCharles *

i guess checking in cargo.lock isn't that uncommon:

$ fd '^Cargo\.lock$' | wc -l
97
06:56:26
@robert:scs.ems.hostRobert Rose changed their display name from Robert Rose - 🌴 04.07 to Robert Rose.07:58:40
@wonrax:matrix.orgwonrax joined the room.08:37:31
@tomasajt:matrix.orgToma

There used to be a lot more but I removed most of them... Anyways:

In this case I think it is fine to eat the bullet if the lockfile is not crazy large.

But in case you really don't want to:

  • Fetch the lockfile from crates-io into your local git checkout, (you may need to remove it from .gitignore first)
  • git add it,
  • run any cargo command that tries to generate the lockfile (e.g. cargo build)
  • generate a patch file via git diff
  • in nixpkgs add the patch file to cargoPatches
  • profit?

At least I think this could work.
You might be better off vendoring the lockfile.

12:31:15
@tomasajt:matrix.orgToma *

There used to be a lot more but I removed most of them... Anyways:

In this case I think it is fine to eat the bullet if the lockfile is not crazy large.

But in case you really don't want to:

  • Fetch the outdated lockfile from crates-io into your local git checkout, (you may need to remove it from .gitignore first)
  • git add it,
  • run any cargo command that tries to generate the lockfile (e.g. cargo build)
  • generate a patch file via git diff
  • in nixpkgs add the patch file to cargoPatches
  • profit? (if the patch is not too large)

At least I think this could work.
You might be better off vendoring the lockfile.

13:00:29
@nbp:mozilla.orgnbp changed their display name from nbp — PTO to nbp.13:11:39
@charles:computer.surgeryCharlesyeah i had considered that, but it seems more convoluted and annoying to maintain14:26:36
@charles:computer.surgeryCharlesi made a PR that vendors the lockfile last night (about 8 hours ago) and it's merged now, so14:27:07
@charles:computer.surgeryCharlesreally wish people would just commit their lockfiles14:27:49
@istipisti113:matrix.orgistipisti113 joined the room.16:32:49
@jackleightcap:matrix.org@jackleightcap:matrix.org left the room.18:09:41
@saiko:knifepoint.netKatalin 🔪 changed their display name from Katalin ⚧︎ to Katalin 🔪.23:28:49

There are no newer messages yet.


Back to Room ListRoom Version: 6