KConfig compiler. GenerateProperties and Mutable.

[Artem Fedoskin]

Hi Aleix,

I'm sorry for late reply. I was trying to compile KStars for Android and
struggled a bit with compiling KF5.

   1. I don't know whether this is a problem or a feature - When I compile
   my app for Android and use KConfig compiled for Android the ARM version
   of kconfig_compiler is executed to build options class. I had to change
   kconfig_compiler executable compiled for Android with the one compiled
   for my system to build options class. Can I somehow specify to CMake
   that I need kconfig_compiler built for my system, not Android and at the
   same time use Android version of KConfig?
   2. I found that mSettingsChanged is included only in kconfig/autotests/
   kconfig_compiler/test_signal.h.ref but there is no mention of it in
   kconfig_compiler.cpp. Could you please tell me what can be the reason
   why val on kconfig_complier.cpp:2061 is 0?
   3. Some of KF5 modules can be compiled using the script provided by KDE
   but unfortunately it doesn't support KIO. I saw from your blog posts
   that you have experience with building for Android. Could you please point
   me where should I start building KIO for Android?

Regards,

Artem Fedoskin

2016-05-10 16:49 GMT+02:00 Aleix Pol <aleixpol at kde.org>:

> On Mon, May 9, 2016 at 8:02 PM, Artem Fedoskin <afedoskin3 at gmail.com>
> wrote:
> > Dear KDE developers,
> >
> > For my GSoC 2016 project at KDE (Lite version of KStars for mobile
> devices)
> > I need to access C++ class generated from XML configure file with KConfig
> > compiler from QML. I found in this patch
> > https://git.reviewboard.kde.org/r/123367/ and in the source code of
> KConfig
> > compiler that I should set GenerateProperties=true in my .kcfgc file to
> > create option properties as Q_PROPERTY. However, I got following error
> "Too
> > many signals to create unique bit masks". There is some conflict between
> > Mutators and GenerateProperties options that causes this error in my XML
> > configure file but I can't figure out what I should change to have
> setters
> > in Q_PROPERTY.
> >
> > Would be grateful if someone could help me with this issue.
> >
> > Options.kcfgc - https://paste.kde.org/pm1klcbls
> >
> > kstars.kcfg - https://paste.kde.org/phit6qibo
>
> Hi Artem,
> KConfigCompiler is limited in this regard by an implementation detail.
> See "uint mSettingsChanged;".
>
> To solve it, I would patch kconfig_compiler and turn it into an
> std::vector<bool> or patch kstars.kcfg to use separate config files
> rather than a huge one.
>
> HTH,
> Aleix
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20160513/79709214/attachment.html>