QTIP Developer Guide
This guide is about how to develop QTIP.
If you just want to use it for performance benchmark, check the user guide instead.
It is recommended to use virtualenv to isolate your development environment from system, especially when you are working on several different projects.
QTIP use tox to automate the testing tasks
Undering macOS system, it will happen to a fatal error when installing package
It is for macOS uses TLS instead of OpenSSL and no header files supported. The solutions is:
Third Party Code
QTIP includes a few third party code via subrepo. All third party code are stored in
To pull the changes from remote repository, use
It will create a new commit in parent repo, i.e.
qtip. However, the auto generated commit message does not include mandatory tags such as
Change-Id required by gerrit. You need to manually amend the commit to append those.
Example of final commit message
Sometimes you may modify the third-party code to adapt it in
qtip. To push the changes to remote repository, run
If you want to include a new repository of third party code. Use