I'm gonna pretend I did not read most of the crap posted
in last couple days, and instead that someone asked
"Hey, what IDE are people using with SDCC",
and I'll tell what works for me.
If you are using windows, and happen to have winavr
installed, then you already have an IDE that works with S
3. Install CDT
4. Install the SDCC plug-in
Just a few thoughts to keep the discussion running.
Regards
Kevin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Gray
Sent: Sunday, 31 August 2008 6:37 a.m.
To: sdcc-user@lists.source
d Erlacher
- Original Message -
From: "Maarten Brock" <[EMAIL PROTECTED]>
To:
Sent: Sunday, August 31, 2008 7:37 AM
Subject: Re: [Sdcc-user] Quickstart document
> Richard(s),
>
> DOS and Windows are no different in this regard. stdin,
> stdout and stderr have been
Richard(s),
DOS and Windows are no different in this regard. stdin,
stdout and stderr have been a part of it since at least
DOS version 2.1 (I've never used an earlier one). And
all this piping works in them too.
Maarten
> stdout (stdin and stderr) are an integral part of stdio.h, so it's as
:
> Yes, but 'C' is a Unix-ism, isn't it?
> - Original Message -
> From: "Richard Gray" <[EMAIL PROTECTED]>
> To:
> Sent: Saturday, August 30, 2008 12:36 PM
> Subject: Re: [Sdcc-user] Quickstart document
>
>
>> stdout (stdin an
Yes, but 'C' is a Unix-ism, isn't it?
- Original Message -
From: "Richard Gray" <[EMAIL PROTECTED]>
To:
Sent: Saturday, August 30, 2008 12:36 PM
Subject: Re: [Sdcc-user] Quickstart document
> stdout (stdin and stderr) are an integral part of stdio.h,
stdout (stdin and stderr) are an integral part of stdio.h, so it's as much a
C-ism as a Unix-ism.
I don't know how the Windows environment would cope with this, but under Unix
file-descriptor 0 is stdin, descriptor 1 is stdout, and 2 is stderr, and
these are automatically opened before the exec
0:39 AM
Subject: Re: [Sdcc-user] Quickstart document,was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richard,
>
> it's a switch you use when you invoke SDCC with intention to redirect its
> output to a file.
>
> If you type:
> C:>sdcc blinkey.c > blinkey.
0:39 AM
Subject: Re: [Sdcc-user] Quickstart document,was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richard,
>
> it's a switch you use when you invoke SDCC with intention to redirect its
> output to a file.
>
> If you type:
> C:>sdcc blinkey.c > blinkey.out
&
Richard,
it's a switch you use when you invoke SDCC with intention to redirect its
output to a file.
If you type:
C:>sdcc blinkey.c > blinkey.out
all the output of sdcc will go to the console window, and blinkey.out will have
size of 0 bytes.
If you type
C:>sdcc --use-stdout blinkey.c > blinkey
e using the same mechanism, and that allows me to
peruse it at my leisure.
regards,
Richard Erlacher
- Original Message -
From: "Jan Waclawek" <[EMAIL PROTECTED]>
To:
Sent: Saturday, August 30, 2008 3:14 AM
Subject: Re: [Sdcc-user] Quickstart document, was: Virus in
SDCC-2.
> > Under W9x, for me it was a challenge to find the --use-stdout switch as
> > the "dosbox" there has no "scrollback" feature, and without this switch
> > it's impossible to redirect the output into a file. This is not an issue
> > under WXP as you can scroll back the "dosbox".
> >
> Couldn't y
- Original Message -
From: "Jan Waclawek" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 29, 2008 5:18 PM
Subject: Re: [Sdcc-user] Quickstart document,was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richard,
>
>>Maybe a few words would be helpful
Richard,
>Maybe a few words would be helpful about what makes one editor more
>"suitable" than another, or what might make it less-suitable. A few
>suggestions as to "convenient" features might be helpful in this context,
>too.
Well, this is not really SDCC-specific...
I don't feel competen
s may change, though.
regards,
Richard Erlacher
- Original Message -
From: "Mark Swayne" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 29, 2008 3:50 PM
Subject: Re: [Sdcc-user] Quickstart document, was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richard Erlach
Richard Erlacher wrote:
>
>> 5. Providing SDCC was completely happy, the output you are looking for is
>> in the same directory (C:\SW\Blinkey), named 'blinkey.ihx', and it is a
>> standard intelhex (note the suffix is different than the standard .hex).
>>
>> Please comment.
>>
>>
> OK ... T
see below, please.
regards,
Richard Erlacher
- Original Message -
From: "Jan Waclawek" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 29, 2008 3:08 PM
Subject: Re: [Sdcc-user] Quickstart document,was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richar
see below, please.
regards,
Richard Erlacher
- Original Message -
From: "Jan Waclawek" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 29, 2008 2:49 PM
Subject: Re: [Sdcc-user] Quickstart document,was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richa
Richard,
>I have a 'C' program, which I hope will work, on paper in my hand ...
Yeah, the BBC (bare-brain-computer). ;-)
>There's a computer running Windows on the desk in front of me. I want to
>compile this program for introduction by whatever means might be available
>into a system based
Richard,
I answer the simulator-specific part separately.
>I've looked for it, but haven't found one that operates as one might expect.
>Perhaps its doc's need clarification. Are there any? I recall reading
>something about a simulator and a link to a website that seemingly no longer
>works.
Jan,
see below, please.
regards,
Richard Erlacher
- Original Message -
From: "Jan Waclawek" <[EMAIL PROTECTED]>
To:
Sent: Friday, August 29, 2008 2:52 AM
Subject: [Sdcc-user] Quickstart document,was: Virus in
SDCC-2.8.0-setup.exe - MD5 etc tutorial
> Richard,
&g
Daniel,
OK the wording was a bit strong, I apologize. On the other hand, as a common
user, spoiled by windowey clickey programs, I somehow cannot get to like a
simulator where for each single step I have to type "step" and hit enter, and
then type in a bunch of other commands to find out, what
On Fri, 29 Aug 2008, Jan Waclawek wrote:
> There _is_ a '51 simulator which comes with SDCC, but it is rather
> cumbersome to use and has a command-line interface only (read: command line,
> no text-screen). It is not intended to be used by human, rather, in an
Excuse me, but I should say that I
Richard,
> [...] and I'd be happy to help generate a more
user-manual-for-Windows-Users sort of document
> that assumes nothing about one's knowledge of LINUX or *NIX,
> and targets those who would prefer to utilize this tool set from Windows
rather than having to move to LINUX,
> if only I could
24 matches
Mail list logo
