Thanks Peter,
This weekend I wrote a quick and dirty program to produce a makefile from the USES clauses in the main pascal program and all the used files. It doesn't support included files.
I then define the environment variable:
RHIDE_COMPILE_LINK_PASCAL_AUTOMAKE=make -f$(subst .exe,.mk,$(OUTFILE))
This seems to work pretty well despite the fact that RHIDE maintains its own list of dependencies.
Following is a sample makefile produced by the command:
mkdep demo ticks.o lgrx20
%.o %.gpi: %.pas gpc -g -c $< all::demo.exe DEPS_demo=colors.gpi objects.gpi cydriver.gpi cyviews.gpi cybutton.gpi windows.gpi plots.gpi axes.gpi graph.gpi arrplot.gpi evedisp.gpi DEPS_colors= DEPS_objects=colors.gpi DEPS_cydriver=colors.gpi objects.gpi DEPS_cyviews=objects.gpi colors.gpi cydriver.gpi DEPS_cybutton=objects.gpi colors.gpi cydriver.gpi cyviews.gpi DEPS_windows=objects.gpi cydriver.gpi cyviews.gpi colors.gpi cybutton.gpi DEPS_plots=colors.gpi coords.gpi clip.gpi objects.gpi cyviews.gpi DEPS_axes=colors.gpi coords.gpi objects.gpi plots.gpi DEPS_graph=objects.gpi plots.gpi axes.gpi DEPS_arrplot=colors.gpi rfarray.gpi objects.gpi cydriver.gpi plots.gpi axes.gpi DEPS_evedisp=colors.gpi objects.gpi cydriver.gpi cyviews.gpi DEPS_coords= DEPS_clip= DEPS_rfarray=colors.gpi objects.gpi coords.gpi plots.gpi axes.gpi OBJS=colors.o objects.o cydriver.o cyviews.o cybutton.o windows.o plots.o axes.o graph.o arrplot.o evedisp.o coords.o clip.o rfarray.o ticks.o demo.o:demo.pas $(DEPS_demo) colors.o colors.gpi:colors.pas $(DEPS_colors) objects.o objects.gpi:objects.pas $(DEPS_objects) cydriver.o cydriver.gpi:cydriver.pas $(DEPS_cydriver) cyviews.o cyviews.gpi:cyviews.pas $(DEPS_cyviews) cybutton.o cybutton.gpi:cybutton.pas $(DEPS_cybutton) windows.o windows.gpi:windows.pas $(DEPS_windows) plots.o plots.gpi:plots.pas $(DEPS_plots) axes.o axes.gpi:axes.pas $(DEPS_axes) graph.o graph.gpi:graph.pas $(DEPS_graph) arrplot.o arrplot.gpi:arrplot.pas $(DEPS_arrplot) evedisp.o evedisp.gpi:evedisp.pas $(DEPS_evedisp) coords.o coords.gpi:coords.pas $(DEPS_coords) clip.o clip.gpi:clip.pas $(DEPS_clip) rfarray.o rfarray.gpi:rfarray.pas $(DEPS_rfarray) demo.exe: demo.o $(OBJS) gpc -odemo.exe -g demo.o $(OBJS) -lgrx20
Russell
-----Original Message----- From: Peter Gerwinski [SMTP:peter@gerwinski.de] Sent: Friday, November 06, 1998 10:24 PM To: Thamm, Russell Cc: gpc@hut.fi Subject: Re: Automake
Thamm, Russell wrote:
I am having so much trouble with automake that I am considering
abandoning
GPC altogether. [...]
:-(
I keep running out of virtual memory on a machine with 256 MBytes of
memory.
This looks like a circular dependency between some units.
Using a makefile is much better.
Our current project (together with the related issue of re-writing the GPI mechanism) is to re-implement the AutoMake mechanism using `make'.
I am not absolutely sure how to express the dependencies.
To get the (*$include ... *) dependencies, run `gpc -M foo.pas'. It will produce a rule
foo.o: foo.pas foobar.incl foobaz.inclyou only need to extend by adding the gpi files of the units used by this one and the action `gpc -c $(PFLAGS) foo.pas'. The result will look like the following:
foo.o: foo.pas foobar.incl foobaz.incl bar.gpi: gpc -c $(PFLAGS) foo.pasMake seems to have no concept of a compilation producing more than one output file.
If you duplicate the rule above for the GPI file,
foo.o: foo.pas foobar.incl foobaz.incl bar.gpi: gpc -c $(PFLAGS) foo.pas foo.gpi: foo.pas foobar.incl foobaz.incl bar.gpi: gpc -c $(PFLAGS) foo.pasthen `make' will nevertheless compile `foo.pas' only once (at least according to my tests with GNU make:-).
I can get RHIDE to bypass automake by not specifying a primary file and adding all source files to the project. But Rhide apparently ignores the Uses
clauses
when determining dependencies and I ca't work out how to use user-defined dependencies with it.
What about producing a Makefile with RHIDE and adding the `uses' dependencies manually?
A library for gpi's would be nice?
Any suggestion how this could be implemented?
Any options to indicate to automake that certain units don't need to
be
checked?
Nope. But if AutoMake does not see the source, it will not try to recompile.
I suspect that if automake kept track of the units not requiring compilation, things might improve.things. That is, the first time it checks grx20.pas, it
should
note that no recompilation is required rather than rechecking the same file many times.
Indeed. That's one reason why we think that `make' should be invoked instead of `gpc1' duplicating the features of `make'.
Greetings,
Peter-- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980830 PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 Fight the SPAM and UBE! - http://spam.abuse.net/ - http://maps.vix.com/