Open Razican opened 6 years ago
How did this file get there?
They get generated in the build.rs
build script. I guess it's good practice to generate the completions in the target directory, right?
Ideally, they should go to OUT_DIR
, but there is no easy way to package those files in the cargo deb
command.
Indeed. Hmm, so cargo-deb needs a good way to distinguish between executables and other executable assets put in the target directory.
I could limit stripping only to native rust targets. Then stripping of everything else specified in package.metadata.deb.assets would be left up to build scripts...
That would be great, yes.
Hi @kornelski! Is there any news on this front?
I haven't got time to implement this. Could you have a look yourself?
There's alredy built_binaries() method that should be plugged in.
OK, I will try to give it a look when I get some free time.
Hi, I just tried this again and it seems fixed. Is this the case?
Ping @kornelski
Hello,
I'm running cargo-deb in the SUPERAndroidAnalyzer/super repository, and I get the following error with three files, all of them command line completions:
The affected files are the following:
super.bash
super.fish
_super