[mpas-developers] COMMIT CHECK: Updated Makefile

Doug Jacobsen jacobsen.douglas at gmail.com
Sat Feb 25 12:06:38 MST 2012


Hi All,

In the ocean development group, we have been discussing making options in
the makefile for debug builds. So, I have attached a proposed revision to
the current makefile structure, in order to make debug, and other modified
builds, easier to maintain.

If you call make incorrectly (without CORE= or a compiler set) you will get
a usage statement now. I collapsed all of the compiler sets (ifort-serial
ifort-serial-papi ifort-papi ifort) into one master set (ifort). My
thoughts here were that it would be easier to maintain a single set of
flags for a compiler than one for each potential version of the compiler. I
also added three "options" to the make process. Which are as follows.

DEBUG=true - Builds a debug version of the code, the default is the
optimized build.
SERIAL=true - Builds a serial (non-MPI) version of the code, the default is
to build the parallel (MPI) version of the code.
USE_PAPI=true - Builds a version of MPAS using the PAPI library for timers
and hardware counters. The default is to not use this.

These can all be appended to make along with the CORE=core option. So, an
example to build a serial debug version of MPAS that uses PAPI libraries
would be
"make gfortran CORE=ocean DEBUG=true SERIAL=true USE_PAPI=true"

Any values for DEBUG, SERIAL, and USE_PAPI that are not "true" invoke the
default options for those.

Please take a look at the attached makefile, and let me know if anyone has
any comments or questions about it. I would like to push this onto the
trunk early next week if possible.

Thanks,
Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/mpas-developers/attachments/20120225/b652d189/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile
Type: application/octet-stream
Size: 8448 bytes
Desc: not available
Url : http://mailman.ucar.edu/pipermail/mpas-developers/attachments/20120225/b652d189/attachment.obj 


More information about the mpas-developers mailing list