Hello Dave, > 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.
You will have to quote them (i.e., use sdcc -mpic14 -p16f877 "C:\Program Files\SDCC\whatever"). If you installed SDCC into a path including spaces, I suppose you need to add proper -I and -L directives to tell SDCC the Include and Library search paths in a quoted manner like sdcc -pic14 -p16f877 -I "C:\Program Files\SDCC\include\pic16" -I "C:\Program Files\SDCC\include" -L "C:\Program Files\SDCC\lib\pic16" -L "C:\Program Files\SDCC\lib" "C:\Program Files\myself\test\etc.c" You might also try to use POSIXish path names using a forward slash as separator instead of a backslash---quotes are still required to mask the space. Specifying paths for source files should only be required if they do not reside in the current directory (use "cd NAME" to change the current directory, e.g. via a relative path NAME). For these include directories and library search paths there should be nice dialog boxes around to set them up, along with arguments (such as -p16f877) to the compiler... But even if all this does go well, there is still the problem of telling gputils/gplink to find its .inc/.lkr files... and of course calling gpasm and gplink in the first place... I'd recommend to reinstall SDCC and gputils into a path with no spaces in them, such as "C:\sdcc". Good luck. > 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? Nope, but as its output is errors and warnings, these go into a different output stream: there's a standard output stream (stdout), which can be redirected and piped through more using the | and > operators, but which receives hardly any output from SDCC, and then there's the standard ERROR output stream (stderr), which cannot easily be redirected using | or >. However, on Linux systems you can redirect the stderr stream via the construct 2>&1 to go to stdout, so maybe sdcc [options here] 2>&1 | more works even on Windows... As I do no (longer) use Windows, I cannot test any of these proposals. Regards, Raphael ------------------------------------------------------------------------- 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
