-
Notifications
You must be signed in to change notification settings - Fork 10
/
Copy pathREADME
78 lines (46 loc) · 2.21 KB
/
README
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
SDL Application Example for use with Qt Creator
-----------------------------------------------
For now, we have to resort to setting up custom build and deploy steps, as the
current SDK version is tightly integrated with Qt Creator and qmake. The steps
are easy, and you can customize each step. "mb2 build" uses the configure,
build and install steps defined in the .spec file, and also makes sure all
build dependencies are installed properly (so list them in the .spec file).
You can also use other build systems (e.g. autotools or cmake) as long as you
state your build-dependencies correctly in the .spec file and as long as you
add the right "configure" command to the %prep step in the .spec file.
The SOURCES, HEADERS and OTHER_FILES variables in the .pro file are used to
display the source files in the Qt Creator IDE. They are not used for building.
Here's how you configure Qt Creator to build the project:
1. Open the .pro file in Qt Creator
2. Modify the project build settings:
General:
Disable the "Shadow build" setting
Build Steps:
Remove ALL steps, then add a new one:
Custom Process Step
Command: sdk/target
Arguments: mb2 build
Working directory: %{buildDir}
Clean Steps:
Remove ALL steps, then add a new one:
Custom Process Step
Command: sdk/target
Arguments: sb2 make clean
Working directory: %{buildDir}
3. Modify the project run settings:
Deployment:
Remove ALL steps (except the "Start Emulator" one), then add a new one:
Custom Process Step
Command: sdk/target
Arguments: mb2 deploy --pkcon
Working directory: %{buildDir}
Run:
Custom Process Step
Command: sdk/target
Arguments: mb2 run /usr/bin/harbour-sdltest
Working directory: %{buildDir}
(if you change the application binary name, you have to customize the
name here; simply replace /usr/bin/harbour-sdltest with
/usr/bin/$APPNAME)
4. If you want to have a target device other than "SailfishOS Emulator",
you need to modify the DEPLOYMENT_DEVICE variable in sdk/target.