setup-venv.sh
--------------
Operation:
	- Creates a virtualenv and installs packages required by CAF and CAF Unit tests
	- Virtual env is created under ~/.virtualenvs/CAF
	- Uses pip for installation. 
	- pip is instructed to use the local cache to find libraries.
	This cache is available under iox-dev/third-party/python27/*
Pre requisites:
	- Assumes that the build/target system has pip, virtualenv installed and
	build tools (gcc, make etc.,) are available.

run-caf.sh
-----------
	- Runs CAF as a python process
	- If ~/.virtualenvs/CAF is available, switches to it before starting to CAF.
	- Else, the required dependencies are assumed to be available on the system.

run-tests.sh
-------------
	- Runs CAF unit tests.
	- Runs coverage, pep8 and pyflakes checks.
	- If ~/.virtualenvs/CAF is available, switches to it before starting to CAF.
	- Output of these runs are captured under <root-folder>/test_output/caf
	which can be used by Jenkins CI for interpretation of results.

CAF on target platforms
-----------------------

1. Installing dependencies
	CAF dependencies can be built as part of the host OS image for the target so
	that they are available as part of the file system.

	If not, the dependencies can be built by a build script into a seperate folder (ex. caf-libs).
	This folder can be shipped along with a CAF tar ball in a structure needed by the platform.
	The run-caf.sh can be modified to setup PYTHONPATH to include such folder before starting CAF.
	Note that the build script may need to do a cross compilation depending on the target platform.

	For ex., on CGR, the dependencies are installed to a local/lib folder which is then packaged
	into the CAF release. Before CAF startup, PYTHONPATH is set to use local/lib folder.

2. Setting up config files
	Generic config files are provided under caf/config.
	These files will need to be modified to suit platform requirements.
	This can be done by a build/package script for a given target platform.

3. Running CAF
	With the required dependencies available, the target platform may use run-caf.sh
	or use APIs provided in caf/src/appfw/runtime/hostingmgmt.py to start CAF.
