-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to build this project? #2
Comments
Place above #![feature(no_std)], this should fix that error. The last time I built was using older rustc - 2 months ago, waiting for 1.0. We can start cleaning this, so lets keep this issue open until the project is in linking complete phase |
Thank's for your advice. However still error...
|
Check this https://github.com/rust-lang/rust/pull/21988/files, feature should be above |
I got some progress! Where is core?
|
Ah , its not written in the readme, check my other rust example, where is written how to build core (its target in the makefile, make libcore) - You need a rust clone to build libcore. https://github.com/0xc0170/frdm-kl25z-rust |
The libcore.rlib was built. However also error occurs.
|
More progress! I think the compile error is an issue of my environment. I'll try to fix it.
|
I built mbed libraries. However linker can't find gpio_write symbol...
|
libmbed.a - library is part of this project. I commited the prebuilt mbed library because I had to do some modifications, I described it here http://0xc0170.github.io/rust/2015/02/18/mbed-with-rust-update-1/ (the very end). I am planning to create an issue on mbed and possibly to send a proposal how we can fix it (don't inline HAL functions and some extensions I found valuable when using rust for example). |
How about commit *.o files?
I think your gitignore file shut out these. |
I got it!
However I doesn't have frdm-k64f board... |
Could you open the patch for mbed? I would like to test your project on LPC1768. |
I'm tring to build your project.
However I stop at following error.
Do you have any infomation for it?
The text was updated successfully, but these errors were encountered: