EndsOfInvention 67 2 You can compare the two toolchains here and here. Also the commands sent to the debugger to configure it could be different.
|Date Added:||2 April 2004|
|File Size:||60.54 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Enough to make the difference between success and failure when trying to use the same source and linker script.
Also both are using gnu make utility - make files will be processed the same way. Memory layouts of data might change, for example, and code that accidentally relied on it would break.
Seen that happen a lot of times. Sign up using Email and Password. Yagatto you are producing an hex file, then this could be different as the two toolchains are not using the same version of newlib library.
Post as a guest Name. You can compare the two toolchains here and here. Also the commands sent to the debugger to configure it could be different.
Email Required, but never shown.
In order to be on the safe side, make sure that in both cases the correct binutils are first in the path. I did not expect any differences and both compile my project happily using the same makefile and.
Sign up using Facebook. However while the Winarm version runs the Yagarto version doesn't.
ELEKTOR FORUMS • View topic - C Programming & ARM Interfacing Books - YAGARTO Toolchain Ch
I agree that the gcc's and the other binaries ld should be the same or close enough for you not to notice the differences. It is possible to aygarto your code and makefile portable, but it takes a few times through this exercise to learn how to do that.