On 14 Nov 2002 at 9:49, Prof A Olowofoyeku (The Afric wrote:
Is anyone else interested in having environment variables for the GPC driver to cover things like "unit-path", etc.? [...] I might well patch the GPC driver for Mingw to do just that....
Actually, this was already possible (with a three-character patch to "lang-specs.h", if I recall the filename correctly) by setting the otherwise-empty "*gpc1" entry in the "specs" file. One could set, e.g.:
-funit-path=F:\Pascal\Units
or
-fobject-path=R:\Global\Objects
in the specs file and automatically add those paths to every GPC compilation (unless --no-unit-path was given for the GPC invocation). I have been using the specs file to include a unit path and also:
-fexecutable-file-name
...so that I don't get "a.exe" if I neglect to specify an output filename. And finally, I had added this (wrapped for clarity only):
%{!fclassic-pascal-level-0:%{!fclassic-pascal: %{!fextended-pascal:%{!fobject-pascal: %{!fborland-pascal:%{!fdelphi:%{!fpascal-sc: %{!fgnu-pascal:-fextended-pascal}}}}}}}}
...to have GPC default to Extended Pascal unless one of the other specifiers appeared on the command line.
Regrettably, though, it appears from the changelog that specs processing has been removed from GPC for this release. It might be easier to reinstate it than to add processing for equivalent environment variables (and specs processing is more flexible as well).
-- Dave