- This topic has 0 replies, 1 voice, and was last updated 2 weeks, 2 days ago by
.
-
Posts
-
This message was transferred over from our old forum)
Posted August 19, 2015
By Todd DeBoer
[hr]
On 11/05/2009 wella asked, ” Do I have to do some changes if I want to compile uEZ with CodeSourcery toolchain for ARM(gcc compiler)? Or just only define a macro COMPILER_TYPE RowleyARM?”
[hr]
(Follow up post)Answered:
Yes, if you are trying to port uEZ to CodeSourcery, you will want to setup a new COMPILER_TYPE macro (assumingly CodeSourcery) and go through the code duplicating sections that select code and macros based on the use of COMPILER_TYPE. Future Designs has not ported the code to CodeSourcey, so you should expect some problems.
I would recommend seeing how well the code compiles for the existing COMPILER_TYPE’s defined under CodeSourcery and make a determination on which is the least amount of work.
- You must be logged in to reply to this topic.
