- Intro and getting started
- Build by convention
- Dependencies and project configuration
- Compile options
- Continuous integration
- Environment variables
- Ignore and exclude
- IDE Integration
- Data Security and Privacy
A tipi.build environment consits of 2 elements:
- CMake toolchain file
- OS image
The OS images are described via the help of Packer files and can be automatically deployed on the tipi.build cloud as many-core build agent or as execution environment for unit test.
Officially supported environments can be found as
<environment>.cmake file pairs in the tipi-build/environments github repository.
While emphasizes on providing a default environment for each major platform, community maintained or private environments are welcome.
As a good starting point tipi always provides at clean and up-to-date clang with libc++ STL for following environments:
tipi build . -t wasm
tipi build . -t linux
tipi build . -t windows
tipi build . -t macos
Variations specifiying C++ standard versions are also available (adding the suffix
.(dot) in the commands above can be any path containing C++ source files or a C++ CMake project.
tipi build . -t linux-cxx17
Will provision an environment as described in
%TIPI_HOME%\<distro>\environments\linux.pkr.js) on the tipi.build and run the build using your tipi subscription.
All required files will be synchronized bidirectionally to and from the tipi build node as necessary.
tipi . -t linux-cxx17
When your machine fits your target environment you can also use the tipi provided toolchain to build locally.
Make use of your subscription to run your application on the remote tipi node:
tipi -t macos-cxx17 .run build/bin/app
- all paramters after
.runare forwarded to the remote environment
- the standard IO is redirected to the calling console
tipi run build/bin/app
Will run a command within the tipi environment on your local machine. Note the abscence of
. in front of
Tipi environments can be customized to your need by creating the required set of CMake toolchain and Packer file.
Examples can be found at tipi-build/environments .
Once they are stored in
tipi build . -t <environment> will start the image creation the tipi cloud and then build the current sources.
Image creation and storage are billed on your subscription. Non-currated images1 are stored for 14 days after the last usage before being evicted from cache. Tipi provides consulting services for the creation of custom images is required, please contact us for more information.
Found an error or want to add more info? Write an issue or contribute changes to this documentation at tipi-build/docs on