It is absolutely the goal that module developers should be able to work against a binary installation of Zorba, and I know that it actually did work at some point in time. I certainly took some pains to make that use case functional when developing the initial non-core module architecture. In particular, I am sure that at some point it was possible to build a non-core module AND run its tests without needing a Zorba build directory.
David, have you actually tried it? Follow the instructions from our documentation:
starting with the "Creating a CMake Module Project" section.
That said, a lot has changed since I last tried it, and I don't think anybody is actually doing development in that fashion. So it wouldn't surprise me to find out that this is currently broken. Also, the particular case of inter-module dependencies is one that has never worked very well, so it may well be that that doesn't work even if simpler modules do. So, I'll take this bug as a reason to check out the current situation and see if there are things to improve.
It is absolutely the goal that module developers should be able to work against a binary installation of Zorba, and I know that it actually did work at some point in time. I certainly took some pains to make that use case functional when developing the initial non-core module architecture. In particular, I am sure that at some point it was possible to build a non-core module AND run its tests without needing a Zorba build directory.
David, have you actually tried it? Follow the instructions from our documentation:
http:// www.zorba- xquery. com/html/ documentation/ 2.1.0/zorba/ modules_ authoring
starting with the "Creating a CMake Module Project" section.
That said, a lot has changed since I last tried it, and I don't think anybody is actually doing development in that fashion. So it wouldn't surprise me to find out that this is currently broken. Also, the particular case of inter-module dependencies is one that has never worked very well, so it may well be that that doesn't work even if simpler modules do. So, I'll take this bug as a reason to check out the current situation and see if there are things to improve.