From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] package: add qt5virtualkeyboard
Date: Thu, 23 Mar 2017 00:46:57 +0100 [thread overview]
Message-ID: <20170323004657.30266283@gmx.net> (raw)
In-Reply-To: <20170322211621.5u6tlemnihszb53s@gportay>
Hello Ga?l,
On Wed, 22 Mar 2017 17:16:21 -0400, Ga?l PORTAY <gael.portay@savoirfairelinux.com> wrote:
[...]
> > > +
> > > +define QT5VIRTUALKEYBOARD_INSTALL_TARGET_CMDS
> > > + mkdir -p $(TARGET_DIR)/usr/lib/qt/plugins/platforminputcontexts
> > > + cp -dpfr $(STAGING_DIR)/usr/lib/qt/plugins/platforminputcontexts/libqtvirtualkeyboardplugin.so $(TARGET_DIR)/usr/lib/qt/plugins/platforminputcontexts
> > > + cp -dpfr $(STAGING_DIR)/usr/qml/QtQuick/VirtualKeyboard $(TARGET_DIR)/usr/qml/QtQuick
> > > + cp -dpfr $(STAGING_DIR)/usr/qtvirtualkeyboard $(TARGET_DIR)/usr
> >
> >
> > Still no $(STAGING_DIR)/usr/qtvirtualkeyboard file to copy:
> >
> > cp: cannot stat ?.../host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/qtvirtualkeyboard?: No such file or directory
>
> Okay, it is certainly because you did not configure it for Japanese/Chinese
> layouts; and I did not clean properly the target directory when I tested it.
>
Yes, enabling this adds some content to $(STAGING_DIR)/usr/qtvirtualkeyboard:
$ find staging/usr/qtvirtualkeyboard/
staging/usr/qtvirtualkeyboard/
staging/usr/qtvirtualkeyboard/pinyin
staging/usr/qtvirtualkeyboard/pinyin/dict_pinyin.dat
And adds additional compile/object files to:
- qt5virtualkeyboard-5.8.0/src/virtualkeyboard/3rdparty/pinyin
- qt5virtualkeyboard-5.8.0/src/virtualkeyboard/3rdparty/openwnn
Both with own license files:
- qt5virtualkeyboard-5.8.0/src/virtualkeyboard/3rdparty/pinyin/NOTICE (Apache License v2.0)
- qt5virtualkeyboard-5.8.0/src/virtualkeyboard/3rdparty/openwnn/NOTICE (Apache License v2.0)
> Will you agree for this if statement?
>
> if [ -d "$(STAGING_DIR)/usr/qtvirtualkeyboard" ]; then \
> cp -dpfr $(STAGING_DIR)/usr/qtvirtualkeyboard $(TARGET_DIR)/usr; \
> fi
Possible (working) solution, but a more deterministic way would be good, see
additional/optional license problem above (and more 3rdparty modules: hunspell,
lipi-toolkit, t9write, tcime)...
Regards,
Peter
>
> >
> > Regards,
> > Peter
> >
> >
> > > + $(QT5VIRTUALKEYBOARD_INSTALL_TARGET_EXAMPLES)
> > > +endef
> > > +
> > > +$(eval $(generic-package))
> >
>
> Regards,
> Gael
next prev parent reply other threads:[~2017-03-22 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 20:54 [Buildroot] [PATCHv3] package: add qt5virtualkeyboard Gaël PORTAY
2017-03-22 21:07 ` Peter Seiderer
2017-03-22 21:16 ` Gaël PORTAY
2017-03-22 23:46 ` Peter Seiderer [this message]
2017-03-24 19:46 ` Gaël PORTAY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170323004657.30266283@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox