see below, please. regards,
Richard Erlacher ----- Original Message ----- From: "Jan Waclawek" <[EMAIL PROTECTED]> To: <sdcc-user@lists.sourceforge.net> 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 > Richard, > >>I have a 'C' program, which I hope will work, on paper in my hand ... > > Yeah, the BBC (bare-brain-computer). ;-) > Yes, we're all supposed to use that ... but how does it help with SDCC? > >>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 on one of the target MCU's supported by SDCC. What's >>my >>first step? ... then what ... ? > > I assume some prerequisites which might not hold true. For example, that > you have some experience with programming under Windows (I don't mean > writing programs for Windows but using Windows-based PC as a host for > cross-development). Please say "stop" if I miss a step. > > 0. Download and install SDCC. > Seems reasonable, and the doc's include considerable info about that. > > 1. Create some suitable directory (aka folder) for your program. For > example, C:\SW\Blinkey. > Sidenotes: > 1a. Micro$oft has some ideas about where you should place files created by > you, like "C:\Documents and Settings\Username\My Documents\something". If > you like that scheme, proceed accordingly. I personally don't like it. > Nor do I. I usually create a "work" directory in the same environment as the software tools I'm using. That way related filenames don't get mixed up from one context to another. There might well be a project in which I'm evaluating several MCU options, so I might have a "workHC0x, and a work5x, and a workZ80 (not likely) directory, all under SDCC. > > 1b. For start, I assume your program will be something simple (blinkey.c), > single-file, includes only the standard headers and local headers, uses no > other than standard libraries etc. All SDCC-generated files will then go > into this directory, together with your sources. Things might get more > complicated later. > > 2. Type in your blinkey.c program, using some suitable editor. > Yes, and let's assume, for now, it's ultimately saved in a project-relevant "working directory" under SDCC. > > 3. Run a command window (a.k.a. DOS window, DOS box). Click Start->Run, in > W9x type "command", in W2k/WXP type "cmd". Go to your directory (e.g. > using "cd C:\SW\Blinkey"). > 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. > > 4. Type 'sdcc blinkey.c' (if the target is 8051, which I assume is your > case). > 4a. If it says 'Bad command or file name', something went wrong during > installation and the path to the SDCC executables did not get into the > PATH environment variable. In this case, you need to type '"C:\Program > Files\SDCC\bin\sdcc" blinkey.c' > > 4b. Enjoy SDCC's opinion on your program :-) > Fortunately, there is already some helpful doc on what those compiler-generated "complaints" might mean. > > 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 ... The path, etc, is a pretty standard thing under Windows, so it's a matter of preference. The target MCU might change ... but not for now. The output includes an ASM file, right? What else should I look for? > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
