|
1220.1.2
by Gord Allott
no, i lied, this time i added the HACKING file |
1 |
If you want to hack on unity you need the following packages |
|
2054.2.1
by Gord Allott
corrected HACKING file |
2 |
- libnux-2.0 |
|
1220.1.2
by Gord Allott
no, i lied, this time i added the HACKING file |
3 |
- libbamf |
4 |
- libdee |
|
5 |
- gio-2.0 |
|
6 |
- dbusmenu-glib-0.4 |
|
7 |
- gthread-2.0 |
|
8 |
- indicator |
|
9 |
- atk |
|
|
2455.4.4
by Alejandro Piñeiro
Reflect on HACKING the new dependency to libatk-adaptor |
10 |
- libatk-adaptor |
|
1220.1.2
by Gord Allott
no, i lied, this time i added the HACKING file |
11 |
|
12 |
Or if you are on ubuntu run the command, apt-get build-dep unity |
|
13 |
||
14 |
Unity uses the google coding style for any C++ code which can be found here: |
|
15 |
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml |
|
16 |
||
17 |
When in doubt copy the coding style of the file you are editing. |
|
18 |
||
19 |
Internal Documentation can be built for Unity by having doxygen installed and running make doxygen - its intended to give a high level understanding of the relationships between different parts of the code, not as a definitive API. doxygen generated files will be stored in api-docs/ |
|
20 |
||
21 |
||
22 |
To build Unity the latest Unity you should grab the source files from bzr with |
|
23 |
bzr branch lp:unity |
|
24 |
||
25 |
then make a directory called build in unity directory. inside that directory run |
|
26 |
CMAKE ../ |
|
27 |
make
|
|
28 |
||
29 |
Please note that this will create a systemwide install of unity, if you are developing localy (you are unless you know different) run |
|
30 |
CMAKE -DCMAKE_INSTALL_PREFIX=~/staging ../ |
|
31 |
||
32 |
changing ~/staging to suit wherever you want to install files locally |
|
33 |
||
|
1761.1.1
by Gord Allott
Updated HACKING file |
34 |
Standalone clients are not built by default, they require substantial build time investments and memory investments (500MB and will double your build time) - however they are very useful for development. to build them you can run the standalone clients make target |
35 |
make standalone-clients all |
|
36 |
||
37 |
or if you have a specific client you care about you can build that client explictly |
|
38 |
make dash |
|
39 |
||
40 |
Testing is handled through GTest, googles test system, we currently have three test targets; test-gtest, test-gtest-xless, test-gtest-dbus. tests that require Nux should be in test-gtest as they require X, tests that can run headless should be in test-gtest-xless and tests that require dbus should be run with test-gtest-dbus, which tests run with our test service. |
|
41 |
||
|
1825.2.11
by Mikkel Kamstrup Erlandsen
Add a remark to HACKING explaining how to enable debug logging |
42 |
To enable debug logging you must set the environment variable UNITY_LOG_SEVERITY to the log domain you |
43 |
want to watch and the log level for that domain. For example: |
|
44 |
||
45 |
UNITY_LOG_SEVERITY="unity.dash.lens=DEBUG" standalone-clients/dash |
|
46 |
||
|
2419.1.2
by Thomi Richards
Added a separate README file for autopilot-running instructions, updated the autopilot shell script, and the HACKING file. |
47 |
If you want to run the autopilot test suite, refer to the instructions in tests/autopilot/README. |
|
1825.2.11
by Mikkel Kamstrup Erlandsen
Add a remark to HACKING explaining how to enable debug logging |
48 |
|
|
1220.1.2
by Gord Allott
no, i lied, this time i added the HACKING file |
49 |
for more information see the README file |
|
1824.1.1
by Didier Roche
dummy commit for ABI rebuild |
50 |