Differences when building with CMake or autotools

[Andrew Davis]

When one builds with Cmake the install locations of certain files and the presence of some files are different than when using autotools.

When building with autotools, a moab_version.h is produced, this is not produced by Cmake

When building with Cmake the produed MOABconfig.make is installed to lib/cmake/MOAB/ whereas with autotools, its installed to lib/

I guess behavior should be consistent either way.

[Vijay M]

Thanks for pointing these out Andy. Yes, the autotools version should be the guiding principle here since it is more widely used. We need to make sure the CMake installation follows similar practices for both the build and installation. If you want to submit a PR, please go ahead.

Else, do let us know all the issues and I'll try to get to it some time before end of this week.

[Vijay M]

@rajeeja this looks like a duplicate of the issue that you created for CMake equivalence with autotools.

[Paul Wilson]

Issue #50 was marked as a duplicate of this issue.

[Paul Wilson]

I have found another difference....

When building with CMake, if IMESH and FBIGEOM are both disabled, it does not define the MOAB_FC_FUNC macro that is needed for LAPACK dependent code (Matrix3)

[Vijay M]

Thanks for this note. I'll check and push a fix. I'm swamped until next Tuesday but will try to get to this soon after.

[Paul Wilson]

This is partially addressed in PR #444.

There remain some differences in the configuration files that are installed between these two build methods:

1. some CMake relevant files are not installed by autotools
2. some autotools relevant files are not installed by CMake

It is not clear that this is possible or advisable.

Also, some of the configuration files are generated in both cases, in the same locations, but differ slightly in their contents.

Two additional differences are spelled out in #112 and #113

‌