Add entry

C34 How can I make sure that one file is compiled before another? For example
    to make sure that an F90 module file "module.F90" is available for other
    file "using.F90".


git-svn-id: http://svn.cactuscode.org/flesh/trunk@3379 17b73243-c579-4c4c-a9d2-2d5706c11dac

1 files changed, 16 insertions, 1 deletions

diff --git a/doc/FAQ b/doc/FAQ
index f122d082..e06ca892 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
 Cactus Code Frequently Asked Questions
 
-$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.68 2003-07-26 14:53:28 schnetter Exp $
+$Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.69 2003-08-18 14:49:40 schnetter Exp $
 
 Also available at http://www.cactuscode.org/Documentation/FAQ
 
@@ -151,6 +151,10 @@ C33 I'm working on a machine where a compiler problem means that I
     need to compile a particular thorn with a lower optimisation level. 
     Is there an easy way to do this? 
 
+C34 How can I make sure that one file is compiled before another? For example
+    to make sure that an F90 module file "module.F90" is available for other
+    file "using.F90".
+
 
 ------------------------------------------------------------------------------
 Running:
@@ -991,6 +995,17 @@ C33 I'm working on a machine where a compiler problem means that I
     will be machine/compiler specific, so you only want to add them for 
     the problematic machine.
 
+C34 How can I make sure that one file is compiled before another? For example
+    to make sure that an F90 module file "module.F90" is available for other
+    file "using.F90".
+
+    Add dependency declarations to the thorn's make.code.deps file, for example
+
+    using.F90.o: module.F90.o
+
+    Note that you have to use the source file names and append the suffix ".o".
+    This convention is different from the default Makefile rules.
+
 
 ------------------------------------------------------------------------------
 Running: