Re: [Sdcc-user] code portability

[Richard E. <ed...@id...>]

Thanks. Frieder, for the guidance.  I'm making very small stepwise motions 
in the direction of getting SDCC to where I can actually use it.

I'm in a lot worse fix than you may realize, however, in that I've yet to 
figure out how to get SDCC to run on a Windows box.  That seems to be the 
only available non-LINUX environment for it.  Sadly, I'm not comfortable 
enough with LINUX to want to venture into that environment.

I've been unable to find out enough about SDCC or GCC or CYGWIN because the 
associated websites are too full of non-information, e.g. glitz, glamour, 
links and advertising, but nothing that explains precisely how and in what 
precise environment (directory config, etc.) these tools have to run.  Can 
you refer me to a site that actually explains this?  I'm not unwilling to 
dedicate an entire computer to a development tool, but (a) I don't want to 
have to learn LINUX, and (b) I don't want to have to interpret someone 
else's code.

I believe I need basic information, simply because, though I've been aware 
of SDCC, GCC, and CYGWIN for several years, I've been unable to find out (1) 
what, EXACTLY, they are, and aren't, (2) what, EXACTLY they do and what role 
they have in the larger scheme of things, and (3) how, EXACTLY, they have to 
be installed/configured/provisioned.

Can you recommend a source of this information?

thanks,

Richard Erlacher
----- Original Message ----- 
From: "Frieder Ferlemann" <fri...@we...>
To: <sdc...@li...>
Sent: Tuesday, August 02, 2005 10:46 AM
Subject: Re: [Sdcc-user] code portability


> Richard Erlacher wrote:
>> Can anybody recommend a PC-compatible compiler that understands the 
>> syntax and function of the SDCC?  I thought I'd seen some comment on this 
>> on the SDCC site, but haven't lately been able to find it.
>
> Hi,
>
> you could "#include <lint.h>" on top of your files.
> This basically removes/translates SDCC specific keywords and
> should ANSIfy your source enough to run gcc or another compiler
> over it.
>
> This might require conversion of your include files to the more
> ANSI compliant style which for example 8052.h uses.
>
> Note, gcc will still stumble over code which contains the __asm; __endasm;
> keyword pair.
>
> RFC: maybe SDCC should also allow inline assembly like __asm(NOP); ?
>
> Greetings,
> Frieder
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Sdcc-user mailing list
> Sdc...@li...
> https://lists.sourceforge.net/lists/listinfo/sdcc-user