D6466: Android: scan for qml files in the source dir, not in the install dir.

[Aleix Pol Gonzalez]

apol accepted this revision.
apol added a comment.
This revision is now accepted and ready to land.


  In https://phabricator.kde.org/D6466#122419, @dfaure wrote:
  
  > In https://phabricator.kde.org/D6466#121152, @apol wrote:
  >
  > > This will be problematic as soon as your application depends on any libraries.
  >
  >
  > You mean, libraries which themselves have installed QML files, right? Depending on e.g. ki18n is no problem.
  >
  > But yeah I can see how this would be a problem for something that depends on kirigami for instance.
  >
  > If we can't find a better solution, then at least it should be documented in the ECM android stuff to NOT put qml files into a .qrc...
  
  
  Yes, that's what I meant.
  
  >> So far we've worked with the assumption that you'd install the applications into a prefix then ran `androiddeployqt` over this file.
  > 
  > Well, that's exactly what I was doing... but if the QML files are built into a .qrc rather than installed, then this fails.
  
  Yes, I understand your problem.
  
  > (The assumption also requires that the install prefix is only used for one android app only, otherwise it would all get mixed up)
  
  Yes.
  
  I've been thinking it through, I agree that the qrc use-case should be properly supported. Let's get this one in and if something's missing we can fix it in `androiddeployqt`.

REPOSITORY
  R240 Extra CMake Modules

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D6466

To: dfaure, apol, mart
Cc: #build_system, #frameworks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20170707/bb268a9b/attachment.html>