new | ask | show | jobs
int_19h a year ago  [ - ]

This sounds very weird to me. Any sane build toolchain should produce a runnable executable that already has +x. What did you use to compile it?

Removing double-click to run an executable binary certainly sounds like something either Gnome or Ubuntu would do, but thankfully that's not the only option in town. In KDE I believe the same exact Windows workflow would just work.

the__alchemist a year ago  [ - ]

>Any sane build toolchain should produce a runnable executable that already has +x. What did you use to compile it?`

`cargo build --release`

Good to know KDE doesn't do that!

int_19h 10 months ago  [ - ]

Even stranger then. Just to make sure I'm not missing something, I just tried this on my Mac:

  $ cargo --version
  cargo 1.86.0

  $ cargo new hello-rs
     Creating binary (application) `hello-rs` package

  $ cd hello-rs && cargo build --release
     Compiling hello-rs v0.1.0 (/Users/int19h/src/hello-rs)
      Finished `release` profile [optimized] target(s) in 0.73s

  $ ls -la target/release/hello-rs
  -rwxr-xr-x@ 1 int19h  staff  468608 May 20 20:16 target/release/hello-rs*

  $ ./target/release/hello-rs
  Hello, world!
Are you sure it's not because the package in question does some kind of weird custom build steps?
the__alchemist 10 months ago  [ - ]

Might have got lost in translation when I moved it from WSL to a windows-made zip file. I think that workflow nukes permissions.