3 ms·
which one generated a 100k binary? I see it running on an uno right here, which has less than 100k https://github.com/avr-rust/arduino https://github.com/avr-ru
by johnny22 9y ago
which one generated a 100k binary? I see it running on an uno right here, which has less than 100k https://github.com/avr-rust/arduino https://github.com/avr-rust/arduino
Were you using zinc or some other project as the base? I figure it is an arm cortex * in your case.
- kennywinker 9y agoI was using the standard rust compiler, plus a bunch of articles on thinning rust binaries. Best I managed was about 80kb after three or four layers of thinning. That link is pretty interesting! The Rev3 uno has 32kb flash, so someone has found a way to thin the binaries enough to fit on an MCU. Cool.. now if only I knew how they did it!
- johnny22 9y agosee how zinc does it https://github.com/hackndev/zinc https://github.com/hackndev/zinc EDIT: Zinc seems to not have been updated in awhile I'm not sure what the current status is of other mcu efforts. I bet some of the other rust folks can elaborate.
- kam 9y agoThe size of a binary statically-linking libstd and targeting a desktop OS has nothing to do with the size of a binary targeting a bare-metal microcontroller where you use only libcore. If you compile for a MCU target with MCU-style code, your code size will be in the same ballpark as the equivalent C++.
- AstralStorm 9y agoHow different is a desktop OS when you're doing syscalls directly (or through a tiny libc) from an embedded OS? See your post sounds like a say so story without data behind it.