andi- changed the topic of #nixos-rust to: buildRustPackage is wrong.
<pie_[bnc]> I feel like im overcomplicating this
<pie_[bnc]> (i have the toml)
<pie_[bnc]> oh maybe i can just use buildrustpackage
<pie_[bnc]> ah wait that wont work without the hash stuff
<pie_[bnc]> bloody heck
<pie_[bnc]> the crate2nix stuff would work if cargo had an inited environment but
<pie_[bnc]> it doesnt
<pie_[bnc]> this is something else actually Error: while retrieving metadata about ./Cargo.toml: Error during execution of `cargo metadata`: error: failed to resolve patches for ``
<pie_[bnc]> oh i should read the rest of the error message
<pie_[bnc]> egh these tools arent built for the sandbox
<pie_[bnc]> and im tired and lost lol
<pie_[bnc]> the problem is the whole fetching from the internet phase and i was hoping one of these tools would just magically handle that , might still be posisble butits not immediately clear to me
Cadey has joined #nixos-rust
<Cadey> hi
<Cadey> i was told to come here by drakonis
<drakonis> hi ho
<drakonis> its a bit quiet atm
<Cadey> je'e
pie_[bnc] is now known as pie
pie is now known as pie_
aleph- has quit [Quit: WeeChat info:version]
aleph- has joined #nixos-rust
drakonis has quit [Quit: WeeChat 2.8]
<andi-> qyliss: yes! Just have to merge it in now iirc
cole-h has quit [Quit: Goodbye]
<pie_> and good morning
<pie_> cargos argument passing is pretty inflexible...
<pie_> and RUSTFLAGS just doesnt hwlp half the time
<pie_> (or its just not showing build script output even with --verbose)
<pie_> (...or its just not getting run at all)
<pie_> apparently cluelessly setting options in a target json will cause rustc to segfault
<pie_> i dont suppose anyone has seen a coherent explicit description of how to build the necessary core libraries for a cross target *without* using xargo? I could try cannibalizing output logs from it but obviously thats not great
<pie_> do i really have to reverse engineer ?
<pie_> arcnmx: most promising option so far ^
<pie_> also xbuild doesnt have an option to not delete its temp files so i dont feel like patching it to figure out why my target options caused a segfault..
<pie_> hm, afaict buildRustCrate doesnt actually build with cargo, so I cant just substitute xargo
<pie_> buildrustpackage does use cargo though so that might be interesting
<pie_> arcnmx: my binaries are probably broken, but the build process,
<pie_> IT LIVES
<pie_> re: xargo is a drop-in replacement
<pie_> more on that later
cole-h has joined #nixos-rust
cole-h has quit [Client Quit]
cole-h has joined #nixos-rust
<pie_> arcnmx: for your consideration
<pie_> example invocation:
<pie_> ah hell stuff gets screwy when you start passing target
drakonis has joined #nixos-rust
<pie_> I seem to be getting a statically linked ELF for some reason and I need a dynamic one though
<arcnmx> hmm o:
pie_ changed the topic of #nixos-rust to: buildRustPackage is wrong. | the ops are those who op those who donut op themselves
<pie_> does anyone know if there's a doc explaining the fields of the target json files?