head	1.2;
access;
symbols
	charm6_1:1.2
	charm_6_0_1:1.2
	charm6_0_1:1.2
	charm6_0:1.2
	ChaNGa_1-0:1.2
	charm5_9:1.2;
locks; strict;
comment	@# @;


1.2
date	2005.01.15.08.55.10;	author gzheng;	state Exp;
branches;
next	1.1;

1.1
date	2003.09.02.22.39.12;	author olawlor;	state Exp;
branches;
next	;


desc
@@


1.2
log
@fixed charmc path
@
text
@CHARMC=../../../bin/charmc $(OPTS) 
OBJS=pgm.o ctests.o 
FOBJS=$(OBJS) ftests.o
COBJS=$(OBJS) ftests_fallback.o

all: pgm 

pgm: $(COBJS)
	$(CHARMC) -o pgm $(COBJS) -language ampi -module fem

fpgm: $(FOBJS)
	$(CHARMC) -o pgm $(FOBJS) -language ampif -module fem

pgm.o: pgm.C
	$(CHARMC) -c pgm.C

ctests.o: ctests.C *.tst
	$(CHARMC) -c ctests.C

ftests.o: ftests.F90 *.tst
	$(CHARMC) -c ftests.F90 -o $@@

ftests_fallback.o: ftests_fallback.C
	$(CHARMC) -c ftests_fallback.C -o $@@

clean:
	rm -f pgm fpgm *.o *.MOD *.mod charmrun

test: pgm
	./charmrun ./pgm +p1 +vp1
	./charmrun ./pgm +p1 +vp2
	./charmrun ./pgm +p2 +vp1
	./charmrun ./pgm +p2 +vp2
	./charmrun ./pgm +p2 +vp3
	./charmrun ./pgm +p2 +vp4
	-@@rm -f fem_mesh_vp3_*
	./charmrun ./pgm +vp3 -write
	./charmrun ./pgm +vp3 -read
	rm -f fem_mesh_vp3_*

test-mig:
	rm -fr pgm pgm.o
	make OPTS="-DENABLE_MIG=1 -memory isomalloc -balancer RandCentLB" pgm
	./charmrun ./pgm +p2
@


1.1
log
@Added this very peculiar set of testing routines--
the ".tst" files are written in a bizarre dialect
that can be preprocessed into either C++ (using the
c_tst.h header) or f90 (using the f90_tst.h header).

The advantage to doing this is that we can write only
one set of testing code, and it automatically works for
C as well as F90, and is guaranteed to work the same way.
This should help prevent the common occurrence where one
or the other language binding is broken.
@
text
@d1 1
a1 1
CHARMC=../../../../bin/charmc $(OPTS) 
@

