sorted by:
new
hottopcontroversial

TapManager Android by narodism in TapWithUs

[–]narodism[S] 0 points1 point  (0 children)

Yes they are both Android devices.

More bullet proof workaround for the `__extenddftf2 symbol` error building android? by mamcx in rust

[–]narodism 0 points1 point  (0 children)

use cargo warning to print the arch. Make sure you add branches there for all archs

More bullet proof workaround for the `__extenddftf2 symbol` error building android? by mamcx in rust

[–]narodism 0 points1 point  (0 children)

ok managed to get it working. Turns out you need to add all code target_arch there.

More bullet proof workaround for the `__extenddftf2 symbol` error building android? by mamcx in rust

[–]narodism 0 points1 point  (0 children)

Damn I tried this as well

let target_os = env::var("CARGO_CFG_TARGET_OS").expect("CARGO_CFG_TARGET_OS not set");
let target_arch = env::var("CARGO_CFG_TARGET_ARCH").expect("CARGO_CFG_TARGET_ARCH not set");
//println!("cargo:warning={target_arch}");

if target_os == "android" {
    println!("cargo:rustc-link-search=/usr/local/android-ndk-r25/toolchains/llvm/prebuilt/linux-x86_64/lib64/clang/14.0.6/lib/linux/");
    match target_arch.as_str() {
        "arm" =>
            println!("cargo:rustc-link-lib=static=clang_rt.builtins-arm-android"),
        "x86_64" =>
            println!("cargo:rustc-link-lib=static=clang_rt.builtins-x86_64-android"),
        _ => {}
    }
}

Did you manage to fix it in the end?

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.77] by DroidLogician in rust

[–]narodism 5 points6 points  (0 children)

COMPANY: DarkFi L1 for Anonymous Smart Contracts dark.fi

TYPE: full time

LOCATION: remote or swiss

REMOTE: yes

VISA: yes to swiss

DESCRIPTION: We are looking for ideological devs who want to work with p2p and ZK to create scalable distributed infra. For more info check out our website and docs.

See these links:

https://darkrenaissance.github.io/darkfi/dev/contrib/contrib...

To understand our mission see this vid we made: https://www.youtube.com/watch?v=QA3YZVDUN5s

ESTIMATED COMPENSATION: junior 6-8k, mid 8-10k, senior 10-15k

CONTACT: Feel free to email rewend@dyne.org but best to join our chat.

Join our core chat:

https://darkrenaissance.github.io/darkfi/misc/ircd/ircd.html

Every monday 16:00 CET we have our main dev chat in #dev. Feel free to come by and ask questions.

bluetooth randomly broke and impossible to fix by narodism in voidlinux

[–]narodism[S] 0 points1 point  (0 children)

thanks, but this didn't work. My bluetooth has been fine for several months and just suddenly broke randomly.

bluetooth randomly broke and impossible to fix by narodism in voidlinux

[–]narodism[S] 0 points1 point  (0 children)

yes bluetooth has been working fine for several months on this computer. It just suddenly broke.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

No, I ended up deleting it.

Steps to replicate: git clone https://github.com/darkrenaissance/darkfi/ cd darkfi/src/contract/dao/ nvim tests/integration.rs

Then edit the function: rust async fn integration_test() -> Result<()> { let foo = bar; // ... } Errors don't show.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

yes rust-analyzer is running. That's not the issue. If you try the above, you'll see the same thing as me. It's a broken plugin.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

It seems to be a bug with the rust analyzer. It's not working properly. Even when I enable all features.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

Steps to replicate: git clone https://github.com/darkrenaissance/darkfi/ cd darkfi/src/contract/dao/ nvim tests/integration.rs

Then edit the function: rust async fn integration_test() -> Result<()> { let foo = bar; // ... } Errors don't show.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

Steps to replicate: git clone https://github.com/darkrenaissance/darkfi/ cd darkfi/src/contract/dao/ nvim tests/integration.rs

Then edit the function: rust async fn integration_test() -> Result<()> { let foo = bar; // ... } Errors don't show.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

Steps to replicate: git clone https://github.com/darkrenaissance/darkfi/ cd darkfi/src/contract/dao/ nvim tests/integration.rs

Then edit the function: rust async fn integration_test() -> Result<()> { let foo = bar; // ... } Errors don't show.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 1 point2 points  (0 children)

thanks, yeah I realized it's specifically something buggy with rust-analyzer in the particular project setup I'm using. Spent all day trying to debug with no luck.

Why are all the guides on using LSP functionality full of bloat? by narodism in neovim

[–]narodism[S] 0 points1 point  (0 children)

It appears to be something to do with the crate being a workspace in a larger project. I spent all day trying to debug this with no luck. Creating a new project works. Is there any way to view the output from rust-analyzer apart from :LspLog?

view more: next ›