| ??? 02/20/10 08:17 Read: times |
#173338 - the framework and implementations Responding to: ???'s previous message |
Erik Malund said:
even cleaner
choose the appropiate .h file (SDCC or Keil) in the appropiate build include the right one As said already in this thread, this "problem" has been already solved by the SDCC developers (namely Maarten Brock). They started to write device-specific headers using macros instead of keywords, and on top include a common header, compiler.h, which expands those macros automagically into the appropriate sequence of keywords, based on detecting the compiler being used (through preprocessor symbols defined by the toolchain itself, unique to the given toolchain). Here is an example of such header for C8051F520 and family. Unfortunately this is work in [slow] progress, so only a few headers are readily available in this form, but it is easy to make one by "reversing" the macro expansion manually, through a find-and-replace in an editor. JW |
| Topic | Author | Date |
| state of SDCC for 8051 | 01/01/70 00:00 | |
| why don't you simply give it a try? | 01/01/70 00:00 | |
| :re why not try | 01/01/70 00:00 | |
| get the newest version | 01/01/70 00:00 | |
| should not be a big deal | 01/01/70 00:00 | |
| Already done | 01/01/70 00:00 | |
| my take | 01/01/70 00:00 | |
| the framework and implementations | 01/01/70 00:00 | |
re: the framework | 01/01/70 00:00 | |
| haven't, but: | 01/01/70 00:00 | |
| I've used it | 01/01/70 00:00 |