1 FWP is built from source files by OCERA Make-System (OMK) [10]. Prior building FWP, default
2 configuration file must be generated by running
6 Then, build process is started by calling
10 in the top-level source directory. If the compilation is successful, the built targets are
11 placed under compiled directory. To create documentation from comments in source files run
12 doxygen from the top-level source directory. The generated documentation files are placed in the
13 compiled/doc directory.
14 The subdirectories of FWP main directory are:
15 • libfwp contains sources of FWP library. The compiled library is called libfwp.a and is
16 placed in compiled/lib/libfwp.a.
17 • fwp mngr contains sources of FWP agent and manager. The built application is called
18 fwpmngr resp. fwpagent and is placed in compiled/bin/fwpmngr and compiled/bin/fwpagent respectively.
19 • tests contains sources of test programs. The built tests are placed in the compiled/bin-tests
22 In order for application to use FWP, in must be linked to libfwp.a library. Further, FWP
23 agent must be launched in every node. FWP agent can be started from command line by:
25 fwpagent -a 192.168.1.1
27 where -a specifies IP address of the
29 There is only one instace of fwp manager running on access point machine and started by command
32 The contents of tests directory is often changing. The actual detailed list of test programs
33 with their descriptions can be found in README file included in the directory.