| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I08abae71668f5829bc623eb04b571dc56cb40557
|
|
|
|
| |
Change-Id: I179247ef796888e4a11c35804e036b5e831ee0b0
|
|
|
|
| |
Change-Id: Ic2d289368ef0b43b5500caad1e829f8e2a681728
|
|
|
|
| |
Change-Id: I8b7f34fd95636fb4b0724ca4ad890484dcc522a8
|
|
|
|
| |
Change-Id: I1a0de7ebff2310ce6c4f2bc34ade2a26c4f5fe63
|
|
|
|
| |
Change-Id: I9ea800aa0de21297a1d12e5b1c27079fd039efbe
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ia3e6cc1426587473c7079c0b20e76cfbd31cfeea
|
| |
| |
| |
| |
| | |
Change-Id: I238604bec632fe15791d29955ef57de943a5e334
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|/
|
|
| |
Change-Id: I9b07a118a4cd622f280aebedffbce613bbaa3a9b
|
|
|
|
| |
Change-Id: Ie3d304c684e9db86aede0c2f8a80d18ec77ab9ba
|
|
|
|
| |
Change-Id: I4dd19ca2588a7fdb2eea378e4c5598408f609799
|
|
|
|
| |
Change-Id: Ibcb3c61d72122e656e59cc7d9b139d58d2d45ad4
|
|
|
|
| |
Change-Id: Ib4886cbae2238a923807f79afa0cf1267fa03d29
|
|
|
|
|
|
| |
Change-Id: Ic8f41f1f365ded474668c1ec8658bd75239269a9
Reviewed-by: Sergio Ahumada <sahumada@blackberry.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
| |
Change-Id: I6b9ba773a3ac4e650e008d5af11a2be1d19aaf8a
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
|
|
The QJNI API's provide an easy way to communicate with Java API's from
C++. The API consists of two classes, QJNIObject which acts as a wrapper
around Java classes and QJNIEnvironment which attaches the current
thread to the Java VM and exposes the Java Native Interface.
Change-Id: I9cdc395249de74f940b75eab9f2bd32347d5d432
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|