1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
/****************************************************************************
**
** Copyright (C) 2013 Digia Plc
** All rights reserved.
** For any questions to Digia, please use the contact form at
** http://qt.digia.com/
**
** This file is part of Qt Enterprise Embedded.
**
** Licensees holding valid Qt Enterprise licenses may use this file in
** accordance with the Qt Enterprise License Agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia.
**
** If you have questions regarding the use of this file, please use
** the contact form at http://qt.digia.com/
**
****************************************************************************/
/*!
//! [setting up usb access]
On Ubuntu Linux you have to grant your development user access to
plugged in devices. This is done by creating a new \e{udev} rule
that allows access to the device via USB. First, run the following
command in a shell:
\code
echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", TAG+="udev-acl"' | sudo tee -a /etc/udev/rules.d/70-boot2qt.rules
\endcode
Now connect the running device to the development host with a USB
cable. (If already connected, disconnect and reconnect the USB
cable after running the command above).
On \B2QA, you can confirm that the connection is working by running
this shell command:
\code
<INSTALL_DIR>/Tools/b2qt/adb devices
\endcode
The output should be a list of connected android devices,
identified with a serial number and a name. Note that the emulator
may be listed as well, its serial number will be its IP and port
number (\c{192.168.56.101:5555}). If your device is missing from
the list, or the serial number is \c{??????}, the connection is
not working properly. If so, check that the device is powered up,
and that the USB cable has been disconnected and reconnected.
The system log files \c{/var/log/udev} and \c{/var/log/syslog} may
provide relevant information in case of connection problems.
//! [setting up usb access]
//! [configuring device kit]
After the hardware has been prepared, there is one final step required
to set up the development tools in Qt Creator for your device.
You have to configure the right device to be used for each \b{Kit}.
To do so, connect your device to your computer via USB and launch
Qt Creator. Then,
//! [steps for device kit]
\list 1
\li Go to \b{Tools > Options > Build & Run > Kits}
\li Select one of the predefined Kits starting with \e{Boot2Qt...}
that matches the type of your device.
\li Select the correct device in the \b{Device} combobox.
\li Click \b{Ok}.
\endlist
//! [steps for device kit]
//! [configuring device kit]
//! [configuring network device]
After the hardware has been prepared, there are final steps required
to set up the development tools in Qt Creator for your device.
To do so, connect your device to network via ethernet cable and launch
Qt Creator. Then,
\list 1
\li Go to \b{Tools > Options > Devices}
\li Click \b{Add...}
\li Select \b{Boot2Qt Device} and Click \b{Start Wizart}
\li Fill in name of the device and network address. Device address can be seen from
\e{Launcher Settings} when device is running \B2Q demo
\li Click \b{Finish}.
\endlist
You also have to configure the right device to be used for each \b{Kit}.
\include b2qt-post-install-setup.qdocinc steps for device kit
//! [configuring network device]
*/
|