| 18 Nov 2021 |
 Mark | i've considered copying the dependency, and changing Cargo.toml, but that's a bit stretch | 21:53:26 |
| Mark | alternatively, i can try fixing this on upstream | 21:53:48 |
 jonringer | you're looking for cargoPatches | 21:54:08 |
| Mark | rusty_v8 build.rs insists on deleting the downloaded .a file now | 21:54:09 |
| jonringer | which will apply before vendoring | 21:54:23 |
| jonringer | downloading a precompiled binary at build time is a no-no. I would create an issue upstream to some how specify it. | 21:55:05 |
| Mark | In reply to @jonringer:matrix.org
which will apply before vendoring before vendoring, in other words when vendored dependencies are not available yet | 21:56:06 |
| Mark | then cargoPatches isn't a thing i'm looking for | 21:56:27 |
| Mark | because i need to patch the vendored dependency, not project (Deno) itself | 21:56:47 |
| Mark | In reply to @jonringer:matrix.org
downloading a precompiled binary at build time is a no-no. I would create an issue upstream to some how specify it. of course, current Deno derivation is downloading prebuilt v8 .a file from github and placing it into a directory where rusty_v8 would download & put it | 21:58:14 |
| Mark | right now rusty_v8 insists on deleting the file | 21:58:35 |
| Mark | alternatively i can just set V8_FROM_SOURCE=1 and build V8 from source | 21:59:24 |
| jonringer | In reply to @mikroskeem:d0.ee
alternatively i can just set V8_FROM_SOURCE=1 and build V8 from source this looks like it tries to build it from a submodule, which is also bad | 22:00:21 |
| jonringer | https://github.com/denoland/rusty_v8 should really allow you a way to just say, "V8_STATIC_LIB=${pkgsStatic.v8}/lib/v8.a" | 22:01:25 |
| jonringer | or even better yet, attempt pkg-config --static --libs v8 | 22:02:27 |
| Mark | hm wait, RUSTY_V8_MIRROR is a thing | 22:05:54 |
| Mark | clearly didn't RTFM enough | 22:06:15 |
| Mark | and so is RUSTY_V8_ARCHIVE | 22:09:10 |
| 19 Nov 2021 |
|  uep joined the room. | 22:30:31 |
|  evils joined the room. | 22:39:24 |
| 20 Nov 2021 |
|  nykw joined the room. | 11:09:46 |
| 23 Nov 2021 |
 Ralith | has anyone got an emacs + rust-analyzer setup that gets them reasonably recent RA builds? | 00:21:36 |
| Mark | that question is quite ambiguous in many ways | 00:37:24 |
| Mark | what is reasonably recent RA for you? if somebody does have such setup, then what? how is this related to nix (do you want a derivation for RA? or one which combines RA with emacs? or...?) | 00:39:36 |
| Ralith | RA itself updates on the order of weeks, so a reasonably recent build would not be drastically slower than that | 02:03:31 |
| Ralith | if somebody does have such a setup, I would obviously like them to share it :P | 02:03:37 |
| Ralith | it is related to nix because the question is trivial unless you are trying to stay within nix | 02:04:03 |
 andi- | i've got it going with nvim and whatever rust-analzyer is in nixpkgs for a couple of months now | 02:04:30 |
| andi- | isn't it just about pointing emcas to the right LSP? | 02:04:45 |
| Ralith | the emacs LSP impl doesn't like the rust-analyzer in stable nixpkgs | 02:05:09 |
