22 Replies
so APPARENTLY, if i ever redirect output from wivrn it breaks stdin
fhkdsbfkuhdsa
and then it crashes
Bruh
SOMEHOW
oh my god
WHYvrb
i don't know how that's even POSSIBLE
well i may try to do wivrn for rust
not carcinized enough
i am rn trying to figure out how to do libusb over rust
because i can't use wifi for anything
but if i pipe
sleep inf into it, it provides an explicit stdin for it that keeps it from breakingand it works in my shell because then it inherits stdin from my terminal
this is one of the dumbest bugs i've ever discovered LMAO
heeheh should I name it WhyVRn?
š
haha might be too confusing
i'm suffering immensely rn XDDD
that took me hours to figure out
what an awful little bug
yeahhhh
okay well lets see if i can get libusb working on rust for android
and if i can i'll try to do wivrn
fuck
whatever android shit i did to get WiVRn to build
made it so that my normal rust android projects no longer build
aaaaaaaaaaaaaaaaaaaa
oh no
ohno
didya check the toolchain stuffs
yee
i think it's my android dependencies/sdk/ndk things that are borekd
OKAY
i managed to get android thing compiling agian
turns out it was actually that i had 2 versionsi of rust installed, and it decided to use the non-rustup one
so now I can actually figure out how to setup libusb and see if i can get data communicating across!
nice!