casa6
Public
Commits
| 68 68 | |
| 69 69 | ``` |
| 70 70 | -bash-4.2$ git clone -q --recursive https://open-bitbucket.nrao.edu/scm/casa/casa6.git |
| 71 71 | ``` |
| 72 72 | |
| 73 73 | #### Build |
| 74 74 | |
| 75 75 | While CASAtools can be built with Python 2, [CASAtasks](https://open-bitbucket.nrao.edu/projects/CASA/repos/casa6/browse) requires Python 3 so it is probably best to build with Python 3 from the start. Make sure that ```-bash-4.2$ which python``` returns a path to the Python 3 executable you want to use because [CASAtasks](https://open-bitbucket.nrao.edu/projects/CASA/repos/casa6browse) builds with this executable. |
| 76 76 | |
| 77 77 | With the CASA build environment set up, the CASAtools module can be built like: |
| 78 + | |
| 79 + | Linux: |
| 78 80 | ``` |
| 79 81 | -bash-4.2$ cd casa6/casatools |
| 80 - | -bash-4.2$ scripts/gcw-pick |
| 82 + | -bash-4.2$ scripts/gcw-pick |
| 81 83 | -bash-4.2$ autoconf |
| 82 84 | -bash-4.2$ ./configure |
| 83 85 | -bash-4.2$ ./setup.py build |
| 84 86 | ``` |
| 87 + | |
| 88 + | Macos |
| 89 + | ``` |
| 90 + | cd casa6/casatools |
| 91 + | scripts/gcw-pick && autoconf && CC=/usr/bin/cc CXX=/usr/bin/c++ ./configure && autoconf && ./configure && ./setup.py build |
| 92 + | ``` |
| 93 + | |
| 85 94 | The `gcw-pick` script adjusts the standard CASA source tree for building with `setup.py`, and once CASAtools is integrated with CASA this step will not be necessary. `gcw-pick` may run for quite a while... |
| 86 95 | |
| 87 96 | A particular version of Python can be selected at configure time like: |
| 88 97 | ``` |
| 89 98 | -bash-4.2$ PYTHON_VERSION=3.4 ./configure |
| 90 99 | ``` |
| 91 100 | but as noted above, [CASAtasks](https://open-bitbucket.nrao.edu/projects/CASA/repos/casatasks/browse) will use whatever version of python is in your path so it is best to configure your ```PATH``` to get a particular version of Python. |
| 92 101 | |
| 93 102 | #### Alternate Developer Build For Linux |
| 94 103 | |