I saw your last message, that you reinstalled in C:\SDCC. That's a good choice, but the 'subst' command still works. E.g.:
subst S: "C:\Program Files\SDCC" That creates a drive S: that is really a subdirectory, but works just like a drive partition. (To remove it: subst /D S: ) <http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/subst.mspx> Also, If switching to GNU/Linux is too frustrating (as you indicated in another message), I would recommend installing the Cygwin environment: <http://cygwin.com/> That's how I made the leap from Win98 to GNU/Linux five years ago. I installed Cygwin and started slowly learning the incredible power of the Bash shell and numerous GNU tools. (I never got any X applications to work under Cygwin on my under-powered PC--YMMV). Now I use only GNU/Linux and shudder at the thought of going back to Windows. Also, with Cygwin installed, your PC is still 100% Windows, so everything else still works the same. Trying to pipe output to 'more' in a Windows command shell is hit or miss. But with Cygwin installed, you can have a bash shell open along with your other Windows windows. Type the same command in it and it will most likely work. -Ken Jackson Dave Baxter writes: > Related to all this.... > > What is SDCC's support of windows long file names? It's burping now on > C:\Program Files\SDCC etc etc, showing the path as "Files\SDCC etc etc" > So, it's now not even finding the source files. > > ..\source\etc.c doesn't work now either, it did 5 minutes ago! > > Confused.... > > > As to the "| More" "feature". I also find that you can't redirect it's > output to a file, as in... > > Aplication.exe > tmp.txt > > > SDCC talking to the bios directly, or what? > > > Dave B. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Ken Jackson > > Sent: Wednesday, September 26, 2007 12:15 PM > > To: sdcc-user@lists.sourceforge.net > > Subject: [Sdcc-user] How to specify chip type (PIC's) ? > > > > The command line shown does not have any -p switch on it. > > > > This sounds 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 command > > from the command prompt in a shell (a 'DOS box') and see if it works. > > > > -Ken Jackson > > > > Dave Baxter writes: > > ... > > > However, try as I might, I can't seem to get the system to > > accept > "-p16f877" where and however I put it, so what's > > the *Exact* selection > procedure please... Can I reference > > it in the source? Or, will it only > be accepted on a > > command line parameter created mystically by > Code::Blocks? > > > > > > I have spent hours looking for help, but the various > > websites are of > next to zero help with this, either SDCC > > or Code::Blocks that is. > > ... > > > -------- > > > Switching to target: default > > > sdcc.exe -mpic14 -mpic14 -mpic14 -I"C:\Program Files\SDCC\include" > > > -c kiss.c -o .objs\kiss.rel > > > No processor has been specified (use -pPROCESSOR_NAME) > > > PIC14 processors and their characteristics: > > ... ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
