cmake build for CASA-ASAP

[Takeshi Nakazato]

Currently, ASAP for CASA is compiled by make system with fixed Makefile. Cross platform build system using cmake must be needed for unified build system on casacore, casa, and asap.

Corresponding to CAS-2668.

[Malte Marquarding]

I think we should move over to cmake altogether. I will look into a standalone build when you have committed your changes.

[Takeshi Nakazato]

I have committed necessary CMakeLists.txt in trunk. Currently, they depend on casa (utilize modules defined in casa) since some packages (e.g. python) should be exactly same version as casa uses.

For standalone build, libatnf must be built from external/atnf, not external-alma/atnf, so that we should add CMakeLists.txt for external/atnf.

How do you plan to define CMakeLists.txt for standalone build? I found several modules in casacore source tree. Do you use them for ASAP? or do you define it to be independent of both casa and casacore?

Anyway, please look at CMakeLists.txt that I checked in.

[Takeshi Nakazato]

I have committed standalone build mode (r1969).

You can build asap by standalone mode as:

$ cd <ASAP_SRC_DIR> $ mkdir build $ cd build $ cmake .. -DSTANDALONE=ON -DCMAKE_INSTALL_PREFIX=<YOUR_INSTALL_ROOT> $ make -j <NUMBER_OF_CORE>

As a result, executables are installed at <YOUR_INSTALL_ROOT>/bin, python modules including _asap.so are installed at <YOUR_INSTALL_ROOT>/python/<PYTHON_VERSION>/asap, and libraries are installed at <YOUR_INSTALL_ROOT>/lib.

I don't know if this is correct path for installation since I have never built ASAP standalone. Could you check cmake files?

One problem in build is that external/atnf cannot build since there may be version mismatch in RPFITS on my local environment. Could you also check that?

[Malte Marquarding]

I had a look at this finally. I think it would be much cleaner using casacore's cmake system.