CODA-Q: A better way to find data files

[stbergmann]

This is based on
https://build.opensuse.org/projects/home:fstrba/packages/collaboraoffice-desktop/files/0001-Standalone-coda-qt.patch by Fridrich Štrba [email protected].

For one, finding the data files should either

• for a scenario where a developer runs the built qt/coda-qt directly from the source tree: use the data files from the source tree (though this will still not support out-of-tree builds); or

• for a scenario where a coda-qt installed into the system (via make install) is run: use the data files installed into the system (i.e., COOLWSD_DATADIR).

And for another, finding the LICENSE.html in the separate collaboraoffice installation should go via LO_PATH, instead of via some relative path.

Change-Id: Ifd01d46229cd90f68f3d6eacb47cd751a08d7310

• Resolves: #
• Target version: master

Summary

TODO

• ...

Checklist

• I have run make prettier-write and formatted the code.
• All commits have Change-Id
• I have run tests with make check
• I have issued make run and manually verified that everything looks okay
• Documentation (manuals or wiki) has been updated or is not required

[stbergmann]

@fridrich, @Quwex, @timar: Any thoughts? Maybe we could find something even better that would even work for a developer's out-of-tree build?

[fridrich]

@fridrich, @Quwex, @timar: Any thoughts? Maybe we could find something even better that would even work for a developer's out-of-tree build?

The out of tree builds could be supported if we made the flag file run-from-build.in and then configure could generate the run-from-build at the configure time. That would put the file into the same place as the built coda-qt, I guess.