"make install" meaningless for non-core modules
Bug #966999 reported by
Chris Hillery
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zorba |
New
|
Medium
|
Chris Hillery |
Bug Description
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 ExternalModuleC
(*) - ExternalModuleC
Changed in zorba: | |
importance: | Undecided → Medium |
Changed in zorba: | |
assignee: | nobody → Chris Hillery (ceejatec) |
To post a comment you must log in.
Probably, ZorbaUse.cmake should call CONFIGURE_FILE() twice for ExternalModuleC onfig.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.