forked from mandeepshetty/iotivity
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Readme.scons.txt
202 lines (154 loc) · 7.61 KB
/
Readme.scons.txt
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
== Quick guide: build and run IoTivity projects on Ubuntu ==
1. Build
Go to the top directory of 'iotivity' project(Note: should always run 'scons'
command in this directory)
Install external libraries:
$ sudo apt-get install libboost-dev libboost-program-options-dev libexpat1-dev libboost-thread-dev uuid-dev libssl-dev
Build release binaries:
$ scons
(Note: C sdk requires tinycbor. Please follow the instruction in the build
message to install tinycbor)
Build debug binaries:
$scons RELEASE=false
Help:
$ scons -h
Clear:
$ scons -c
2. Run the samples
$ export LD_LIBRARY_PATH=<iotivity>/out/linux/x86_64/release
Run the c++ samples in <iotivity>/out/linux/x86_64/release/resource/examples
Run the c samples in <iotivity>/out/linux/x86_64/release/resource/csdk/stack/samples/linux/SimpleClientServer
('<iotivity>' is the path to 'iotivity' project. If your device is x86, arm,
or arm64, please change 'x86_64' to the proper arch)
== How to build IoTivity projects ==
IoTivity includes a series of projects. You can find all these projects here:
https://gerrit.iotivity.org/gerrit/#/admin/projects/
You can build IoTivity project on Linux / Windows / MAC OSX for various OS(
Linux, Tizen, Android, Arduino, Windows, MAC OSX, IOS ...).
The output of the build is in:
<top directory of the project>/out/<target_os>/<target_arch>/<build_type>/
e.g.
iotivity/out/android/armeabi-v7a/release/.
This document takes 'iotivity' project as example, the way to build other
projects is almost the same.
=== IoTivity project build tool scons ===
Scons is a cross-platform build tool, its usage is quite similar to GNU make.
To build a project, you just require to run following command at the directory
where a SConstruct file exists(SConstruct is the entrance of scons build, it's
equivalent to Makefile of 'make') :
$ scons [options] [target]
In additional, usually the scons build script of a project provides useful help
information(include build options). To see the help information:
$ scons [options] -h
Note: If no value is specified for an option, the default value will be used.
The change of options value may impact the help information and the behavior
of the building.
Generally, it's required to specify the target OS and target ARCH, that's to say
tell Scons which OS and which ARCH you'd like build this project for. By default,
the target OS and ARCH is the same as the host.
Some more options may be required, please care the 'error' notification when build.
For help about how to set an option, please run:
$ scons TARGET_OS=xxx TARGET_ARCH=yyy [XXX=zzz ...] -h
=== Prerequites ===
* 1. Scons
Please refer to the following page to install scons:
http://www.scons.org/doc/production/HTML/scons-user.html#chap-build-install
(Note: on Windows, install Python 2.x before installing scons)
* 2. IDE/SDK Prerequites
To build for some OS (Android / Arduino / IOS ...), an IDE/SDK may be required,
please go to the relative page to download and install the required IDE/SDK.
Android:
To build for Android, Andorid NDK and SDK are required.
Android NDK: http://developer.android.com/tools/sdk/ndk/index.html
Android SDK: http://developer.android.com/sdk/index.html
(Note: as in some IoTivity projects, C++11 features are used, recommend Android
NDK >= r10)
Arduino:
To build for Arduino, Arduino IDE is required.
Arduino IDE: http://arduino.cc/en/Main/Software
(Note: recommend install Arduino IDE >=1.5.8)
Arduino builds are dependent on latest Time library. Download it from here:
http://www.pjrc.com/teensy/td_libs_Time.html
and extract to <arduino_ide_root>/libraries/
(Note: If you are using Arduino IDE 1.5.8 BETA on Windows, it may pop up some
dll isn't found. please copy relative dll from the IDE directory to
C:\Windows\SysWOW64. IDE 1.5.7 doesn't have this issue. Other version IDE isn't
tested.)
Apple:
To build for Mac OSX or IOS, Xcode is required.
Xcode: https://developer.apple.com/xcode/downloads/
Java:
To build the Java code, JDK is required.
JDK: http://www.oracle.com/technetwork/java/javase/downloads/index.html
(If the project doesn't include Java code or you wouldn't like build the
Java codes, this isn't required)
(Note: for convenience, suggest add the IDE/SDK path in environment variable,
so you don't need to add it in command line each time. The build script will
guide you to do that.)
Tizen:
To build for tizen platform tinycbor library is needed.
Please download tinycbor if it is not present in extlibs/tinycbor folder
by doing the following:
$ git clone https://github.com/01org/tinycbor.git extlibs/tinycbor/tinycbor
* 3. External libraries
IoTivity project depends on some external libraries, such as boost, expat ...
During building, the existence of external library will be checked, if it doesn't
exist, the build script will try to download, unpack and build the library or
notify user to install it.
Downloading and unpacking may fail due to network problem or required unpacking
tool isn't installed. An message will be displayed, please follow the message
to skip it.
=== Build IoTivity project on Linux(Ubuntu) ===
1. Build IoTivity project for Linux
$ cd <top directory of the project>
$ sudo apt-get install libboost-dev libexpat1-dev libboost-thread-dev libssl-dev
$ scons
2. Build IoTivity project for Android
$ cd <top directory of the project>
$ scons TARGET_OS=android TARGET_ARCH=xxx
(xxx can be x86, armeabi, armeabi-v7a, armeabi-v7a-hard. To see all of its
allowed value, please execute command 'scons TARGET_OS=android -Q -h')
3. Build IoTivity project for Arduino
$ cd <top directory of the project>
$ sudo apt-get install dos2unix
$ scons TARGET_OS=arduino TARGET_ARCH=xxx BOARD=yyy SHIELD=zzz
(xxx can be avr, arm; yyy is the name of the board, zzz is the shield type, to
get allowed values run: scons TARGET_OS=arduino TARGET_ARCH=xxx SHIELD=zzz -h.
You may see a option 'CPU' in the output of above command line, that's due to
some boards have different processors, to specify the processor, add 'CPU=zzz'
in the command line. If no 'CPU' option exists, that means the board only
support one kind of processor, it's unnecessary to specify it)
4. Build Iotivity project for Tizen
$ cd <top directory of the project>
$ sh gbsbuild.sh
(we provide the spec file required by gbs tool at toools/tizen directory.
gbs is default build tool for Tizen platfrom, we can refer the following
wiki to setup Tizen development environment:
https://source.tizen.org/documentation/developer-guide/getting-started-guide)
Note: Currently most IoTivity project doesn't support Windows, so you can't set
TARGET_OS to 'windows' except the project support Windows.
That's to say if the project doesn't support Windows, run:
$ scons TARGET_OS=windows ....
or run on Windows
$ scons
may always fail.
=== Build IoTivity project on Mac OSX ===
1. Build IoTivity project for Mac OSX
$ cd <top directory of the project>
$ scons SYS_VERSION=yyy
(yyy is the OSX version, e.g. 10.9)
2. Build IoTivity project for Android(It's the same as on Ubuntu)
$ cd <top directory of the project>
$ scons TARGET_OS=android TARGET_ARCH=xxx
(xxx can be x86, armeabi, armeabi-v7a, armeabi-v7a-hard)
3. Build IoTivity project for IOS
$ cd <top directory of the project>
$ scons TARGET_OS=ios TARGET_ARCH=xxx SYS_VERSION=yyy
(xxx can be i386, x86_64, armv7, armv7s, arm64, yyy is IOS version, e.g. 7.0)
Note:
1) for convenience, a script (auto_build.sh) is provided to run possible build
at once. Following is the usage:
To build:
$ auto_build.sh <path-to-android-ndk>
To clean:
$ auto_build.sh -c