[En-Nut-Discussion] Ethernut to Codevision porting

[Hans de Roode]

Hello Harald,
Had a look at porting to codevision, but I have to decline, it's to much
work, codevision is to different from GNU and ICC.
I bought a AVR-ICC licence.

Regards,  Hans



-----Original Message-----
From: Harald Kipp [mailto:harald.kipp at egnite.de] 
Sent: Thursday, 16 September 2004 9:57 p.m.
To: Ethernut User Chat (English)
Subject: Re: [En-Nut-Discussion] Ethernut to Codevision porting


Hans,

haven't looked to Codevision for some time (years?).
The neuralgic parts for porting to another compiler are
(in no particular order):

- inline assembler
- const keyword
- data in code space
- interrupt routines
- pointer to routines within structures
- port access
- context switch (possibly the most difficult part)

In case you consider contributing your changes (highly appreciated),
I'll accept limited changes to the code. Like I did for ICCAVR, see
CONST and INLINE instead of const and inline. But I hate most of the
#ifdefs, with which the code is already contaminated. Please try to
avoid them and use compiler.h instead.

Note, that the Configurator allows to create header files
and specific Makefiles. As far as possible I'll help.

Harald

P.S.: There had been many attempts in this direction,
but except a port of a very early release done by Pavel
Haiduc himself for a customer, nothing appeared. No
idea why people gave up. Same applies to IAR, btw.

At 21:32 16.09.2004 +1200, you wrote:
>Hi all,
>Has anybody ported version 3.6 to Codevision?
>If not, what's involved, just sit down and work trough the compile 
>error's?
>
>
>Regards,  Hans.
>
>New Zealand

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion