Hi,
On Tue, Feb 16, 2010 at 11:45 AM, Maurice Lombardi Maurice.Lombardi@ujf-grenoble.fr wrote:
In fact for that reason, in my personal works I always use the option -o blah.exe. This causes no extra typing because I work in an editor able to launch a compiler with a single click through a script like
#! /bin/sh echo $MSYSTEM gp $(basename "$1" | tr [A-Z] [a-z]) \ -o $(basename "$1" | sed -e 's/(.*).[^.]*$/\1.exe/') \ $2 -march=prescott \ --unit-path=. --unit-path=c:/lombardi/$MSYSTEM/gpc/pascal_u \ --unit-path=c:/$MSYSTEM/units \ --unit-destination-path=c:/lombardi/$MSYSTEM/o \ `head -n 1 "$1" | sed -e '/^[^"]*$/d;s/^[^"]*"//;s/"[^"]*$//'` \ 2>&1 | sed ':1;s,/[^/.][^/]*/../,/,;t 1'
Whew! Perl, where are you when we need you? :-) Anyways, you could probably also use sed instead of tr and head; that would be cleaner, IMHO. But I'm not very *nix savvy, so who cares. ;-)
$2 is --autobuild or nothing
--autobuild even when using GP? Or was that meant to be "gpc"?
As editor I have used in DOS/Windows TextPad, FPE, Context, in Linux gedit, SCite .... These editors (at least those I use now) generate an error buffer and are able to open directly the proper file and put the carret at proper place when clicking on an error message. Very probably there are many others (I never tried OS X for example), and many are free.
For the record, I was unable to figure out compilation from within PENG. Besides, it (DOS version) whines upon startup in NT (Vista), something about printer or something silly like that.
Normally I just use TDE, which isn't really good at capturing error messages, but it does have a quasi-method for supporting such (execute "redir -eo gpc ...", capture output into window, press Ctrl-F7).
Another better option is GNU Emacs 23.1, which indeed compiles and works fine for DJGPP again, so "M-x compile" and " C-x ` " both work as expected (or mouse). Both have Pascal syntax highlighting (although Emacs actually has separate pascal.el and delphi.el). Of course, there is still no standard .ZIP package for 23.1 yet (I have to make one for them!), so that's annoying (180 MB sources unpacked, even the main .EXE is 8 or 9 MB, heh. I made a slim install for myself using "only" 12 MB, woot!).