Tipi helps tackling the biggest challenges in native app development :

• Dependencies management and reliable build caching
• Building and iterating fast
• Cross-platform build and testing

by giving developers:

• Smart dependencies fetching and build caching: no need to wait for packages
• Powerful cross-platform parallel build and test cloud environments
• Build toolchain fully included for Linux, macOS, and Windows platforms

Build from sources without the cost

• Automatic CMake build caching connected to git
• Zero setup - just coding
  • select one environment from our supported list or specify your own
  • tipi downloads & installs the compiler and libraries in an isolated distro folder automatically

Environments on demand

We automatically provision repeatable build environments on powerful cloud build machines when you need them. Learn more about how tipi environments are specified: environment

Every project is a library

In a software project there are 2 kinds of entry-points:

• Developer entry-points for code reuse
• End-user entry-points for application use

By default tipi automatically builds both a library and an application (if something like a main() is found) from your sources to ease reuse.

Don't pay for what you don't use

This is a core C++ design philosophy, and sadly the world of packages manager obliges you to take more than you need.

By definition a package does pack of a lot of things, and the final application won't need all of them.

tipi allows you to do a fine-granular selection of your dependencies and pulls only the bits that are really required in your final application.

Opinionated defaults (but you choose)

While tipi clearly is set out to enable you to build anything without complex scripts (it can generate CMake build scripts from code scan conventions), we don't hold you back to customize parts (or all of) the build with your own CMakeLists.txt files associated with use-cmake.tipi files.

tipi installation location ( former TIPI_HOME_DIR )

When launching tipi for the first time tipi¹ will be installed at:

• On Windows: C:\.tipi\
• On other platforms: /usr/local/share/.tipi/

tipi will install dependencies, environment descriptions and tools for your environments in that location.

I case you want to specify an alternate location (if you don't have much space or no permission to write to that part of the disk) you should use the mechanisms of file-system junctions and bind mounts.

The reason for this, is that tipi guarantees the paths even in non-containerized builds to enable reuse of cached builds artifacts anywhere.