Schell Carl Scivally

Changing `build.rs` as above allows the library to build, but the test suite doesn't link. It seems that libtflite is still being built for x86_64. I have multiple linker errors...

It also seems that `std::process::Command` may be selecting the `x86_64` shell https://github.com/rust-lang/cargo/issues/9158, which causes `make` to set tensorflow's Makefile::HOST_ARCH variable to `x86_64`.

I was building w/ my editor which was causing cargo to choose an `x86_64` shell, which in turn set the host architecture to `x86_64`. After making the initial target change...

@azw413 I've just been maintaining my own fork :(

It also looks like planck and specs are iterating over 10,000 more components than bevy and legion - bevy, legion and shipyard omit the "just A" archetype. bevy: https://github.com/rust-gamedev/ecs_bench_suite/blob/master/src/bevy/schedule.rs#L33-L39 legion:...

Removing the first 10,000 insertions of just A improves planck's peformance by 14%!

I would appreciate this as well. I'm trying to set up my raspberry pi zero w as a bluetooth keyboard with: ```rust let return_classes = client.set_device_class( *controller, DeviceClass::Peripheral { keyboard:...

I think it's possible but difficult without already knowing a good amount about bluetooth development.

Yes, it seems weird. In the meantime I'm using the cli as a backup.

I think it's notable that the `0x2000` part of `0x2540` sets the device in limited discovery mode. I thought maybe the problem was that setting `0x540` when the device is...