Luca Barbato

> I'm trying to compile a project named `rav1e` - I have a script that automatically downloads the source, sets the environment needed for compilation, and then invokes `cargo build`...

I looked at it again. `cargo cbuild` is equivalent to `cargo build --target x86_64-unknown-linux-gnu` in your case, so the way to pass rustflags by env should be over `CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_RUSTFLAGS`. So...

if you do `cargo build --target x86_64-unknown-linux-gnu` you have the same problem. Today and the past days are hectic, so I cannot lookup which is the correct env var to...

Once https://github.com/rust-lang/cargo/issues/9452 hits stable your problem would be solved.

The normal libdir __IS__ `/usr/local/lib`, adding a quasi-chost is a distribution-specific choice and I'm not aware of ways to know which it is which short of checking how they patched...

Sounds like a fair amount of code who's willing to look into porting it? I wonder if would make sense making a separate crate for it.

@eli-schwartz can you link the meson heuristics? Probably it could be distilled in a stand alone crate so other tools may use it for the same purpose.

If you have a timeslice to convert to a patch and send it would be great since I have plans to make a release soon due cbindgen ^^;

Maybe a great example would be taking in a ts and convert it to a cbr one or the leanest vbr one by adding/removing the stuffing?

As example that's exactly what you want :) In a case you read everything, if you find stuffing do not write the packet, otherwise write down what you just read,...