Indeed, much better :) I'm still struggling with finding the proper
documentation at times (do others have the issue with the documentation
table being to wide for the layout and thus having to be scrolled

Best regards,
Lars Ivar Igesund

On Wed, Aug 9, 2017 at 10:26 AM Christian Kandeler <christian.kande...@qt.io>

> On Wed, 09 Aug 2017 08:13:33 +0000
> Lars Ivar Igesund <lars...@gmail.com> wrote:
> > I'm trying to convert a somewhat big qmake based project to qbs. The next
> > challenge is that we have some text files from which we generate C++
> and/or
> > qml files.
> >
> > I have created a module for this that I depend on and configure for the
> > products that need it. The products are all C++/Qt based, but most also
> > with QML components embedded in a resource file. The normal QML files
> work
> > fine, but I'm a bit at a loss for how to include the generated QML file
> in
> > the resource file. (The C++ files are generated and added properly.)
> >
> > In Qmake, the reference to the generated file was always present in the
> qrc
> > file, and then the extra compiler stuff doing the generation depended on
> > the input, and also had target_predeps set. Thus the generated file was
> > eventually present when RCC was run.
> That sounds strange. Why not generate the qrc file instead? Just tag
> your generated QML files as "qt.core.resource_data", possibly set some
> of the related properties (see the resource-specific stuff in
> http://doc.qt.io/qbs/qt-modules.html#core-properties), and you should be
> all set.
> Christian
> _______________________________________________
> Qbs mailing list
> Qbs@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qbs
Qbs mailing list

Reply via email to