Skip to content
Source repository for the QtPods project.
Branch: master
Clone or download
Latest commit 27b1949 Sep 4, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
qt-pods-cli Update main.cpp Mar 3, 2017
qt-pods-core @ 59c2227 Refactored some code and updates. Apr 29, 2016
qtwaitingspinner @ 2efe082 Added managed podinfo. Feb 9, 2015
.gitignore Initial commit Jan 27, 2015
.gitmodules Some refinements. Jun 25, 2016
.podinfo Some refinements. Jun 25, 2016
.travis.yml Add svg dependency to .travis.yml Jun 29, 2016
LICENSE Initial commit Jan 27, 2015 Update Sep 4, 2018
architecture.png Added architecture diagram. Jan 30, 2015
screenshot.png Updated screenshot. Feb 26, 2015

Build status


See the video that demonstrates how easy it is to embed foreign code and write a complete code with auxiliary functions in less than five minutes.

Example video

qt-pods is an attempt to unify the packaging of fragments of Qt sources. Inspired by the cocoapods project, each "pod" follows a strict rule of how its contents are made up, so everyone can easily package her/his code and share it with other developers.


#qtpods on

Mailing list

How to build

Clone repository recursively:

git clone --recursive

Then run:

qmake && make

For system-wide installation run as root in the folder the executable is located in:

make install

pod rules

  • The fragment name is all lower-case and is equal to the repository name.
  • The distribution of the source within the pod is up to the developer.
  • The repository root contains a *.pro file that is a static lib template.
  • The *.pro must have exactly have the same name as the repository.
  • The repository contains a *.pri file that contains instructions for the final target (for example linker flags of dependencies).
  • The resulting library must be in the root of the repository after it has been built.
  • Pod names should start with "qt", ie. "qtfoo".
  • The repository must contain a LICENSE file with the license at root.
  • The repository must contain a file at root.

For developers


Each time you develop an app you will set up a Qt subdirs project. Each pod you are using will be added as a git submodule, thus keeping track of the commit-exact version of the pods you are using.

qt-pods will generate a pods.pri next to the subdirs project. By design, all you need to do is integrating the following statement into your target application's pro file:


The pods.pri will set up the include paths, linker flags against pods and even draw in the dependencies of pods via their pris.

Sometimes you want to have submodules that are not pods. In order to allow that, qt-pods manages all subdir targets in a separate file called pods-subdirs.pri. Usually, if you start a new project from scratch using qt-pods, qt-pods will take care of that and create a subdirs pro with the repository name and include the following statement:


If you have an existing project, you need to put in that line manually.

How does qt-pods compare to inqlude?

At first sight these projects are very similar, but they aren't at all. inqlude's mission is to get an overview of libraries. Inqlude contains a set of meta-information how a certain library is being installed on a certain system - systemwide. Inqlude tries to gracefully wrap around everything to get it working somehow - even if it finally needs to compile libraries from source.

In contradiction, qt-pods' scope is the project. You add pods to a projects and qt-pods will set up a code repository that will keep working even when someone who doesn't use qt-pods wants to build your project. Libraries will be put together at the time you are cloning a repository, and they will be gone when you don't work on a project anymore. qt-pods expects that pods are in a certain format, rather than abstracting away differences through a manifest.


Please be careful. This software is in early state, use it with caution. Make backups of your repositories.

Ideas, improvements?

Let me know at

You can’t perform that action at this time.