zorba-coders team mailing list archive

[Chris Hillery <966999@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: zorba
     Importance: Medium
         Status: New

** Changed in: zorba
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/966999

Title:
  "make install" meaningless for non-core modules

Status in Zorba - The XQuery Processor:
  New

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
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zorba/+bug/966999/+subscriptions