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
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
|
# Create your first AGL application
## Setup
Let's use for example helloworld-native-application, so you need first to clone
this project into a directory that will be accessible by `xds-server`.
Depending of the project sharing method:
- Cloud sync: you can clone project anywhere on your local disk,
- Path mapping: you must clone project into `$HOME/xds-workspace` directory.
<!-- note -->
> **Note** : [helloworld-native-application](https://github.com/iotbzh/helloworld-native-application) project is an AGL
project based on [app-templates](https://git.automotivelinux.org/apps/app-templates/)
(included as a git submodule). This CMake templating, used to develop application
with the AGL Application Framework, will automatically generate makefile rules
(eg. `remote-target-populate`) or scripts (eg. `build/target/xxx` scripts).
For more info about app-template, please refer to [this documentation](http://docs.automotivelinux.org/docs/devguides/en/dev/reference/sdk-devkit/docs/part-2/2_4-Use-app-templates.html).
<!-- endnote -->
### Clone project
```bash
cd $HOME/xds-workspace
git clone --recursive https://github.com/iotbzh/helloworld-native-application.git
```
### Declare project into XDS
Use XDS Dashboard to declare your project. Open a browser and connect to XDS
Dashboard. URL depends of your config, for example `http://localhost:8000`
Click cog icon ![](./pictures/xds-dashboard-icon-1.png){:: style="display:inline; padding:0;"}
to open configuration panel and then create/declare a new project by with the
plus icon
![](./pictures/xds-dashboard-icon-2.png){:: style="display:inline; padding:0;"}
of `Projects` bar.
Set `Sharing Type` and paths according to your setup.
![](./pictures/xds-dashboard-prj-1.png){:: style="width:90%;"}
<!-- note -->
>**Note:** when you select `Path mapping`, you must clone your project into
`$HOME/xds-workspace` directory (named "Local Path" in modal window) and
"Server Path" must be set to `/home/devel/xds-workspace/xxx` where xxx is your
project directory name. If you select `Cloud Sync`, you can clone your project
where you want on your local disk.
<!-- endnote -->
## Build from XDS dashboard
Open the build page (icon ![](./pictures/xds-dashboard-icon-3.png){:: style="display:inline; padding:0;"}), then select your **Project** and the **Cross SDK** you want to use and click on
**Clean / Pre-Build / Build / Populate** buttons to execute various build actions.
![](./pictures/xds-dashboard-prj-2.png){:: style="width:90%;"}
## Build from command line
You need to determine which is the unique id of your project. You can find
this ID in project page of XDS dashboard or you can get it from command line
using the `--list` option. This option lists all existing projects ID:
```bash
./bin/xds-exec --list
List of existing projects:
CKI7R47-UWNDQC3_myProject
CKI7R47-UWNDQC3_test2
CKI7R47-UWNDQC3_test3
```
Now to refer your project, just use --id option or use `XDS_PROJECT_ID`
environment variable.
You are now ready to use XDS to for example cross build your project.
Here is an example to build a project based on CMakefile:
```bash
# Add xds-exec in the PATH
export PATH=${PATH}:/opt/AGL/bin
# Go into your project directory
cd $MY_PROJECT_DIR
# Create a build directory
xds-exec --id=CKI7R47-UWNDQC3_myProject --sdkid=poky-agl_aarch64_4.0.1 --url=http://localhost:8000 -- mkdir build
# Generate build system using cmake
xds-exec --id=CKI7R47-UWNDQC3_myProject --sdkid=poky-agl_aarch64_4.0.1 --url=http://localhost:8000 -- cd build && cmake ..
# Build the project
xds-exec --id=CKI7R47-UWNDQC3_myProject --sdkid=poky-agl_aarch64_4.0.1 --url=http://localhost:8000 -- cd build && make all
```
To avoid to set project id, xds server url, ... at each command line, you can
define these settings as environment variable within an env file and just set
`--config` option or source file before executing xds-exec.
For example, the equivalence of above command is:
```bash
# MY_PROJECT_DIR=/home/seb/xds-workspace/helloworld-native-application
cd $MY_PROJECT_DIR
cat > xds-project.conf << EOF
export XDS_SERVER_URL=localhost:8000
export XDS_PROJECT_ID=CKI7R47-UWNDQC3_myProject
export XDS_SDK_ID=poky-agl_corei7-64_4.0.1
EOF
xds-exec --config xds-project.conf -- mkdir build
# Or sourcing env file
source xds-project.conf
xds-exec -- mkdir -o build && cd build && cmake ..
xds-exec -- cd build && make all
```
<!-- note -->
>**Note:** all parameters after a double dash (--) are considered as the command
to execute on xds-server.
<!-- endnote -->
## Build from IDE
First create the XDS config file that will be used later by xds-exec commands.
For example we use here aarch64 SDK to cross build application for a Renesas
Gen3 board.
```bash
# create file at root directory of your project
# for example:
# MY_PROJECT_DIR=/home/seb/xds-workspace/helloworld-native-application
cat > $MY_PROJECT_DIR/xds-gen3.conf << EOF
export XDS_SERVER_URL=localhost:8000
export XDS_PROJECT_ID=cde3b382-9d3b-11e7_helloworld-native-application
export XDS_SDK_ID=poky-agl_aarch64_4.0.1
EOF
```
### NetBeans
__Netbeans 8.x :__
- Open menu **Tools** -> **Options**
- Open **C/C++** tab, in **Build Tools** sub-tab, click on **Add** button:
![Add new tool panel](./pictures/nb_newtool.png)
- Then, you should set **Make Command** and **Debugger Command** to point to xds tools:
![Add new tool panel](./pictures/nb_xds_options.png)
- Finally click on **OK** button.
- Open menu **File** -> **New Project**
- Select **C/C++ Project with Existing Sources** ;
Click on **Next** button
- Specify the directory where you cloned your project and click on **Finish** button to keep all default settings:
![Select Model panel](./pictures/nb_new-project-1.png)
- Edit project properties (using menu **File** -> **Project Properties**) to add a new configuration that will use XDS to cross-compile your application for example for a Renesas Gen3 board)
- in **Build** category, click on **Manage Configurations** button and then **New** button to add a new configuration named for example "Gen3 board"
![Select Model panel](./pictures/nb_new-project-2.png)
- Click on **Set Active** button
- Select **Pre-Build** sub-category, and set:
- Working Directory: `build_gen3`
- Command Line: `xds-exec -c ../xds-gen3.conf -- cmake -DRSYNC_TARGET=root@renesas-gen3 -DRSYNC_PREFIX=/opt ..`
- Pre-build First: `ticked`
- Select **Make** sub-category, and set:
- Working Directory: `build_gen3`
- Build Command: `xds-exec -c ../xds-gen3.conf -- make remote-target-populate`
- Clean Command: `xds-exec -c ../xds-gen3.conf -- make clean`
![Select Model panel](./pictures/nb_new-project-3.png)
- Click on **OK** button to save settings
By changing configuration from **Default** to **Gen3 board**, you can now simply
compile your helloworld application natively (**Default** configuration) or
cross-compile your application through XDS for a Renesas Gen3 board (**Gen3 board** configuration).
### Visual Studio Code
Open your project in VS Code
```bash
cd $MY_PROJECT_DIR
code . &
```
Add new tasks : press `Ctrl+Shift+P` and select the `Tasks: Configure Task Runner` command and you will see a list of task runner templates.
And define your own tasks, here is an example to build [unicens2-binding](https://github.com/iotbzh/unicens2-binding) AGL binding based on cmake (_options value of args array must be updated regarding your settings_):
```json
{
"version": "0.1.0",
"linux": {
"command": "/opt/AGL/bin/xds-exec"
},
"isShellCommand": true,
"args": [
"-url", "localhost:8000",
"-id", "CKI7R47-UWNDQC3_myProject",
"-sdkid", "poky-agl_aarch64_4.0.1",
"--"
],
"showOutput": "always",
"tasks": [{
"taskName": "clean",
"suppressTaskName": true,
"args": [
"rm -rf build/* && echo Cleanup done."
]
},
{
"taskName": "pre-build",
"isBuildCommand": true,
"suppressTaskName": true,
"args": [
"mkdir -p build && cd build && cmake -DRSYNC_TARGET=root@renesas-gen3 -DRSYNC_PREFIX=/opt"
]
},
{
"taskName": "build",
"isBuildCommand": true,
"suppressTaskName": true,
"args": [
"cd build && make widget"
],
"problemMatcher": {
"owner": "cpp",
"fileLocation": ["absolute"],
"pattern": {
"regexp": "^(.*):(\\d+):(\\d+):\\s+(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"column": 3,
"severity": 4,
"message": 5
}
}
},
{
"taskName": "populate",
"suppressTaskName": true,
"args" : [
"cd build && make widget-target-install"
]
}
]
}
```
> **NOTE** You can also add your own keybindings to trig above tasks, for example:
> ```json
> // Build
> {
> "key": "alt+f9",
> "command": "workbench.action.tasks.runTask",
> "args": "clean"
> },
> {
> "key": "alt+f10",
> "command": "workbench.action.tasks.runTask",
> "args": "pre-build"
> },
> {
> "key": "alt+f11",
> "command": "workbench.action.tasks.runTask",
> "args": "build"
> },
> {
> "key": "alt+f12",
> "command": "workbench.action.tasks.runTask",
> "args": "populate"
> },
> ```
>
> More details about VSC keybindings [here](https://code.visualstudio.com/docs/editor/tasks#_binding-keyboard-shortcuts-to-tasks)
>
> More details about VSC tasks [here](https://code.visualstudio.com/docs/editor/tasks)
#### Qt Creator
Please refer to [agl-hello-qml](https://github.com/radiosound-com/agl-hello-qml#clone--build-project) project.
Thanks to Dennis for providing this useful example.
#### Others IDE
*Coming soon...*
|