[MITgcm-devel] make cleean Clean and CLEAN

[Ed Hill]

On Thu, 2003-11-20 at 12:03, Alistair Adcroft wrote:
> I just did a make CLEAN to move a set-up from one machine to another and
> discovered that whereas we used to only need to move Makefile and data for
> the simplest set-up we now have to move upteen files including a sed script,
> three copies of ad_something.something which are all different,
> FC_MANGLTHING.h defining a single macro, etc...

Or, you could re-run genmake2.  Or you could use tar and make a copy of
the entire directory.


>  a) The Makefile generates AD_CONFIG.h under the target "clean:". What is
> this about?

Recent versions of genmake2 now produce Makefiles with additional
targets to automate various adjoint builds.  They haven't yet been
documented since I'm still working on them in order to produce a new
"testreport" (or similar program) for the adjoint examples.


>  b) I can't compile the model without AD_CONFIG.h - what is this about if
> I'm a forward modeller?

Again, please just run (or re-run) genmake2 and all the files will be
there.


>  c) why is there an AD_CONFIG.template and an ad_config.template?
>  d) why is there an svd_config.template that is never used by anything I can
> see?

Again, this is part of the adjoint build process.


>  e) FC_NAMEMANGLE.h is very ugly. I think this needs to be done via the
> command-line -D

OK, that I'll be happy to change.


> To start reducing the number of files left over after a make CLEAN, I'm
> going to:
>  1) move adjoint_sed out of genmake and into tools/
>  2) add more files to the Clean and CLEAN targets

What difference does it make having a few files left over?  This is not
a rhetorical question.  I want you to explain what harm any of those few
files are dong to anything that you're working on.


> I now see the folly in using .h files for configuration rather than using
> the command-line (you recall it was my preference for configuring packages).
> We are heading down a path where the Makefile is no longer enough to build
> the model and we're seeing an explosion of new files needed just to build.
> Ideally, all information necessary to build should be in the Makefile and
> and it used to be this way; PACKAGES_CONFIG.h breaks that and I'm wondering
> what to do about it.

I'm running a low fever today (so I didn't come in), but please call me
at 339-927-6897 and lets discuss before you rearrange things.

Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://mitgcm.org/pipermail/mitgcm-devel/attachments/20031120/e4018076/attachment.sig>