"make install" meaningless for non-core modules

[Chris Hillery]

It is intended that it be possible for a non-core module project to be build outside of a Zorba build, by setting CMAKE_PREFIX_PATH appropriately to find Zorba. Zorba does export a ZorbaConfig.cmake file in its install image for this purpose.

However, it's not at all clear what "make install" should do for such a project. Moreover, several things provided by Zorba, such as ExternalModuleConfig.cmake.in (*), don't get used in a fashion appropriate for using the module anywhere but its own build directory.

(*) - ExternalModuleConfig.cmake.in is used by Zorba's use file to automatically create a fooConfig.cmake for a project foo.

[Chris Hillery (ceejatec)]

Probably, ZorbaUse.cmake should call CONFIGURE_FILE() twice for ExternalModuleConfig.cmake.in - once with values appropriate for loading from the build directory, once with values appropriate for loading from the install directory. However, this is fairly difficult since the relative paths may change radically. See Zorba's own config/CMakeLists.txt and config/ZorbaConfig.cmake.in; it's not a very pretty setup.