Hi...
Yes, I have Cygwin too, not on this PC though. I got it for the sshd
facility a couple of years ago, a very good robust fallback VPN whenever
I need it. Mind you, installing that was not painless either, needing
several downloads and builds to get all the bits needed working
correctly.
Thanks for all that Raphael...
I sort of pre-empted you with the re-install, to C:\SDCC as you
suggested...
I'll work through the rest as I go, probably doing all the donkey work
with a batch file, as I normally try to keep all my project files in
their unique directories, so I will need to speci
applications: it is sometimes unpredictable.
> Are you sure you want to continue with Windows?
>
> Regards
>
> JP
>
> Le Mercredi 26 Septembre 2007 13:56, Dave Baxter a écrit :
> > Related to all this
> >
> > What is SDCC's support of windows long file n
>
> This shoulds like a Code::Blocks problem, not an SDCC problem.
> There is a forum site where you could post the question and
> you might get more helpful answers: <http://forums.codeblocks.org/>
>
> As an experiment, you could just issue the correct com
Hi Ken...
Sort of agree that the problem may be caused by the way C::B builds the
command line, but it's SDCC's output that shows the use of the -p
option, not C::B's.
The C::B forum's and web pages I've found so far (including that not
very welcoming one) have not been of any help. Lot's of peo
] On Behalf Of
> Robert Bergfors
> Sent: Wednesday, September 26, 2007 11:54 AM
> To: sdcc-user@lists.sourceforge.net
> Subject: Re: [Sdcc-user] How to specify chip type (PIC's) ?
>
> Lainaus Dave Baxter <[EMAIL PROTECTED]>:
>
> >
> > When I try a build (ex
Hi...
Dumb newbie time I'm afraid...
I have SDCC (version unknown, but downloaded, built, installed a week or
three ago) running within Code::Blocks (V1 RC2) and am having trouble
(like cant seem to do it) getting the system to select a chip to build
for.
When I try a build (existing code from a
