|
1 |
|
2 Before the productised infrastructure code hits the MCL, |
|
3 the following locations apply and procedures must be |
|
4 followed in order to use the transport, node, message |
|
5 and the MeshMachine code. |
|
6 |
|
7 1) CBR: |
|
8 Get a green vFuture build excluding comms-infras, |
|
9 networking, ser-comms-c32, i.e: using the command: |
|
10 > getenv -o gt_techview_baseline M0XXXX_Symbian_OS_vFuture -x comms-infras_* -x networking_* -x ser-comms_c32 |
|
11 or |
|
12 > getenv -o gt_techview_baseline M0XXXX_Symbian_OS_vFuture |
|
13 but in this case you will have to perform additional tasks for 2)... |
|
14 |
|
15 abld reallyclean |
|
16 abld cleanexport |
|
17 remove relevant files as in 1b) if listed. |
|
18 |
|
19 ...then continue with 2) |
|
20 |
|
21 1b) optional: |
|
22 Delete everything in epoc32/include/comms-infras except commsdebugutility.* and /commdb directory (3 items). |
|
23 This is to avoid any duplicate headers in different locations. |
|
24 If you run cleanenv, the CBR may copy the CBR versions of comms-infras instead of the productisation ones. |
|
25 |
|
26 2) P4 sync from: |
|
27 //EPOC/DV3/team/2006/convergedcomms/projects/productisation/common/ |
|
28 |
|
29 3) abld build winscw udeb: |
|
30 //EPOC/DV3/team/2006/convergedcomms/projects/productisation/common/bld.inf |
|
31 |
|
32 4) abld test build winscw udeb: |
|
33 //EPOC/DV3/team/2006/convergedcomms/projects/productisation/common/comms-infras/Elements/Unittests/group |
|
34 |
|
35 5) epoc32/data/epoc.ini: |
|
36 Add "startupmode 1". |
|
37 This will cause the emulator to run in console mode, |
|
38 preventing loading of nonexisting comms libraries. |
|
39 |
|
40 6) The demo application can be launched directly: |
|
41 \epoc32\release\winscw\udeb\testnode.exe. |
|
42 |
|
43 Debugging Notes: |
|
44 Relevant breakpoints: all implementations of ReceivedL() (under //EPOC/DV3/team/2006/convergedcomms/projects/productisation/common/comms-infras/Elements/Unittests) |
|
45 show when nodes received messages and then processed them. |