Hello, I have written a small app for school that uses a small module (written by me) and crt. It compiles fine with --automake, but I need to have a Makefile. My problem is that I don't know how to tell make to find crt.pas & co.
should I move crt.pas, gpc.pas and all files they depend on into the build directory?
/Mattias Ãstergren
mattias/spikboll wrote:
Hello, I have written a small app for school that uses a small module (written by me) and crt. It compiles fine with --automake, but I need to have a Makefile. My problem is that I don't know how to tell make to find crt.pas & co.
should I move crt.pas, gpc.pas and all files they depend on into the build directory?
No.
`gpc --print-file-name=units' will output the directory name (igf installed correctly). In GNU make, something like this should work:
GPC_UNIT_PATH:=$(shell $(PC) $(PFLAGS) --print-file-name=units)
If it must work with other makes, I don't know what will work -- in the worst case, a recursive make invocation might do, something like:
all: $(MAKE) GPC_UNIT_PATH=`$(PC) $(PFLAGS) --print-file-name=units` progs
Of course, you could also put `gpc --automake' into the Makefile if that's "allowed" ...
Frank
Oops! My original reply went via "Reply" rather than "Reply All"... Sorry. I will need to fix that sometime.
Try this:
all: <all-of-your-source-files> gpc --automake -o <outfile> <program-file>.pas
Or, if you are *really* deep into this:
crt: crt.o crt.gpi gpc -c /full/path/to/crt.pas
(etc.) --- Frank Heckenbach frank@g-n-u.de wrote:
mattias/spikboll wrote:
Hello, I have written a small app for school that uses a small
module (written by me) and crt.
It compiles fine with --automake, but I need to have a Makefile. My problem is that I don't know how to tell make to find crt.pas &
co.
should I move crt.pas, gpc.pas and all files they depend on into
the build directory?
No.
`gpc --print-file-name=units' will output the directory name (igf installed correctly). In GNU make, something like this should work:
GPC_UNIT_PATH:=$(shell $(PC) $(PFLAGS) --print-file-name=units)
If it must work with other makes, I don't know what will work -- in the worst case, a recursive make invocation might do, something like:
all: $(MAKE) GPC_UNIT_PATH=`$(PC) $(PFLAGS) --print-file-name=units` progs
Of course, you could also put `gpc --automake' into the Makefile if that's "allowed" ...
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707
===== ======= Frank D. Engel, Jr.
__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
Frank D. Engel, Jr. wrote:
crt: crt.o crt.gpi gpc -c /full/path/to/crt.pas
That would mean hard-coding a system path in a project Makefile which is generally not a good idea since the Makefile will only work on one (or few) system(s).
Frank
On Tue, 10 Dec 2002 00:57:24 +0100 Frank Heckenbach frank@g-n-u.de wrote:
Frank D. Engel, Jr. wrote:
crt: crt.o crt.gpi gpc -c /full/path/to/crt.pas
That would mean hard-coding a system path in a project Makefile which is generally not a good idea since the Makefile will only work on one (or few) system(s).
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707
I think I'll "cheat" and go with --automake in the Makefile.
Thank you everyone for the help!
-
Frank D. Engel, Jr. -
Frank Heckenbach -
mattias/spikboll