GEOS-5 Checkout and Build Instructions (Heracles): Difference between revisions
Created page with "These instructions presume checking out the current AeroChem group tag: '''AeroChem-Heracles-5-2_b5'''." |
No edit summary |
||
| Line 1: | Line 1: | ||
These instructions presume checking out the current AeroChem group tag: '''AeroChem-Heracles-5-2_b5'''. | These instructions presume checking out the current AeroChem group tag: '''AeroChem-Heracles-5-2_b5'''. | ||
== How to Check Out and Build the Code == | |||
=== Find a place to store and build the code === | |||
The GEOS-5 (AGCM) source code checks out at about 55 MB of space. Once compiled, the complete package is about 1.3 GB. Your home space on '''discover''' may not be sufficient for checking out and building the code. You should consider either 1) requesting a larger quota in your home space (call the tag x6-9120 and ask, telling them you are doing GEOS-5 development work) or 2) building in your (larger) nobackup space (recommended). But consider, ''nobackup'' is not backed up. So be careful... | |||
One strategy I like is to check the code out to my ''nobackup'' space, but then make symlink from him home space back to that. For example, if I have my code stored at $NOBACKUP/GEOSagcm, I would make a symlink in my home space to point to that like: | |||
% ln -s $NOBACKUP/GEOSagcm GEOSagcm | |||
Revision as of 09:55, 29 June 2016
These instructions presume checking out the current AeroChem group tag: AeroChem-Heracles-5-2_b5.
How to Check Out and Build the Code
Find a place to store and build the code
The GEOS-5 (AGCM) source code checks out at about 55 MB of space. Once compiled, the complete package is about 1.3 GB. Your home space on discover may not be sufficient for checking out and building the code. You should consider either 1) requesting a larger quota in your home space (call the tag x6-9120 and ask, telling them you are doing GEOS-5 development work) or 2) building in your (larger) nobackup space (recommended). But consider, nobackup is not backed up. So be careful...
One strategy I like is to check the code out to my nobackup space, but then make symlink from him home space back to that. For example, if I have my code stored at $NOBACKUP/GEOSagcm, I would make a symlink in my home space to point to that like:
% ln -s $NOBACKUP/GEOSagcm GEOSagcm