I'm working on the next version of embedded-test, which is a test runner for no_std targets. 
Now, I would like to add some compiler test ("ui tests") for my proc macros, to test some features combinations etc.... 
Trybuild seems perfect for that. 

Problem 1: Trybuild builds the compile tests for my host arch (x86) not the target arch. This can be overwritten by setting the env variable `CARGO_BUILD_TARGET`  before calling `TestCases::{pass,compile_fail}`.
Problem 2: When building the trybuild test (that later runs the compile tests), it will include all my no_std crates, which will cause the compilation to fail.  

So I was wondering if I'm still on the right path with trybuild. I need to run my compile tests for my target arch, which has some dependencies that will simply not compile on the host arch...