2021-09-14 14:51:57 +08:00
# setup-cpp
2021-09-14 14:57:47 +08:00
Install all the tools required for building and testing C++/C projects.
2021-09-14 14:51:57 +08:00
![Build Status (Github Actions) ](https://github.com/aminya/setup-cpp/workflows/CI/badge.svg )
2021-09-14 17:40:04 +08:00
2021-09-17 19:29:58 +08:00
Setting up a **cross-platform** environment for building and testing C++/C projects is a bit tricky. Each platform has its own compilers, and each of them requires a different installation procedure. This package aims to fix this issue.
2021-09-14 17:40:04 +08:00
2021-09-17 19:29:58 +08:00
This package is designed to be **modular** and as **minimal** as possible. This will allow you to install the tools you want. It is continuously tested on Windows, Linux, and macOS.
2021-09-14 17:40:04 +08:00
2021-12-07 00:38:38 +08:00
The package can be used locally or from CI services like GitHub Actions.
2021-09-14 17:40:04 +08:00
2021-09-17 19:29:58 +08:00
# Features
2021-09-16 20:15:17 +08:00
2021-09-17 19:29:58 +08:00
`setup-cpp` can install all of these tools:
2021-09-16 18:00:16 +08:00
2021-09-17 19:29:58 +08:00
- cmake
- ninja
2021-12-05 22:56:34 +08:00
- llvm
- gcc
- msvc
2021-12-05 22:20:14 +08:00
- vcvarsall
2021-11-22 00:49:22 +08:00
- vcpkg
2021-09-17 19:29:58 +08:00
- meson
- conan
2022-01-31 06:40:11 +08:00
- make
2022-01-31 07:33:48 +08:00
- task
2021-09-17 19:29:58 +08:00
- ccache
- cppcheck
2022-01-30 06:44:43 +08:00
- clangtidy
- clangformat
2021-09-17 19:29:58 +08:00
- doxygen
- gcovr
- opencppcoverage
2021-12-07 19:30:33 +08:00
- kcov
2022-02-06 12:20:36 +08:00
`setup-cpp` can also install the following. These are automatically installed if needed for the above Cpp tools (e.g., python is required for conan).
2021-09-17 19:29:58 +08:00
- python
- choco
- brew
2022-02-06 12:20:36 +08:00
- sevenzip
2022-02-14 11:30:41 +08:00
- graphviz
2021-09-16 18:00:16 +08:00
2021-09-17 23:27:08 +08:00
# Usage
2022-01-30 07:13:52 +08:00
## From Terminal
2021-09-18 02:24:17 +08:00
2021-11-22 04:20:51 +08:00
You should download the executable file or the js file (if Nodejs installed), and run it with the available options.
2021-09-18 02:24:17 +08:00
2021-11-22 04:20:51 +08:00
Tip: You can automate downloading using `wget` , `curl` , or other similar tools.
2021-09-18 02:24:17 +08:00
### Executable
2022-04-16 17:51:35 +08:00
Download the executable for your platform from [here ](https://github.com/aminya/setup-cpp/releases/tag/v0.11.0 ), and run it with the available options.
2021-09-18 04:40:13 +08:00
2021-11-22 02:11:26 +08:00
An example that installs llvm, cmake, ninja, ccache, and vcpkg:
2021-09-18 04:40:13 +08:00
2021-09-18 10:42:56 +08:00
```ps1
# windows example (open shell as admin)
2022-04-16 17:51:35 +08:00
curl -LJO "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp_windows.exe"
2021-11-22 02:11:26 +08:00
./setup_cpp_windows --compiler llvm --cmake true --ninja true --ccache true --vcpkg true
2022-01-18 10:51:14 +08:00
2022-03-12 09:48:28 +08:00
RefreshEnv.cmd # activate cpp environment variables
2021-09-18 02:24:17 +08:00
```
2021-09-18 10:42:56 +08:00
```ps1
# linux example
2022-04-16 17:51:35 +08:00
wget "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp_linux"
2021-09-18 10:42:56 +08:00
chmod +x setup_cpp_linux
2021-11-22 02:11:26 +08:00
sudo ./setup_cpp_linux --compiler llvm --cmake true --ninja true --ccache true --vcpkg true
2022-01-18 10:51:14 +08:00
2022-03-12 09:48:28 +08:00
source ~/.cpprc # activate cpp environment variables
2021-09-18 10:42:56 +08:00
```
```ps1
# mac example
2022-04-16 17:51:35 +08:00
wget "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp_mac"
2021-09-18 10:42:56 +08:00
chmod +x setup_cpp_mac
2021-11-22 02:11:26 +08:00
sudo ./setup_cpp_mac --compiler llvm --cmake true --ninja true --ccache true --vcpkg true
2022-01-18 10:51:14 +08:00
2022-03-12 09:48:28 +08:00
source ~/.cpprc # activate cpp environment variables
2021-09-18 02:24:17 +08:00
```
2022-03-01 19:04:33 +08:00
NOTE: In the `compiler` entry, you can specify the version after `-` like `llvm-11.0.0` . For the tools, you can pass a specific version instead of `true` that chooses the default version
2021-09-19 01:05:52 +08:00
2022-03-01 19:09:55 +08:00
NOTE: On Unix systems, when `setup-cpp` is used locally or in other CI services like GitLab, the environment variables are added to `~/.cpprc` . You should run `source ~/.cpprc` to immediately activate the environment variables. This file is automatically sourced in the next shell restart from `~/.bashrc` or `~/.profile` if `SOURCE_CPPRC` is not set to `0` . To deactivate `.cpprc` in the next shell restart, rename/remove `~/.cpprc` .
2022-03-01 19:04:33 +08:00
NOTE: On Unix systems, you will not need `sudo` if you are already a root user (e.g., in a GitLab runner or Docker).
2022-01-18 10:51:14 +08:00
2021-09-18 02:24:17 +08:00
### With Nodejs
2022-04-16 17:51:35 +08:00
Download the `setup_cpp.js` file form [here ](https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp.js ), and run it with the available options.
2021-09-18 02:24:17 +08:00
2021-12-07 00:31:23 +08:00
On Windows:
2021-09-18 10:42:56 +08:00
2021-12-07 00:31:23 +08:00
Open the shell as admin, download via `curl` , then install
2021-12-07 16:46:07 +08:00
2021-09-18 10:42:56 +08:00
```ps1
# open shell as admin
2022-04-16 17:51:35 +08:00
curl -LJO "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp.js"
2021-11-22 02:11:26 +08:00
node ./setup_cpp.js --compiler llvm --cmake true --ninja true --ccache true --vcpkg true
2022-01-18 10:51:14 +08:00
2022-03-12 09:48:28 +08:00
RefreshEnv.cmd # activate cpp environment variables
2021-09-18 02:24:17 +08:00
```
2021-09-18 10:42:56 +08:00
On Linux or Mac:
```ps1
2022-04-16 17:51:35 +08:00
wget "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp.js"
2021-11-22 02:11:26 +08:00
sudo node ./setup_cpp.js --compiler llvm --cmake true --ninja true --ccache true --vcpkg true
2022-01-18 10:51:14 +08:00
2022-03-12 09:48:28 +08:00
source ~/.cpprc # activate cpp environment variables
2021-09-18 10:42:56 +08:00
```
2022-01-30 07:13:52 +08:00
## Inside GitHub Actions
2021-09-17 23:27:08 +08:00
2021-12-07 00:41:50 +08:00
Here is a complete cross-platform example that tests llvm, gcc, and msvc. It also uses cmake, ninja, vcpkg, and cppcheck.
2021-09-17 23:27:08 +08:00
`.github/workflows/ci.yml` :
```yaml
name: ci
on:
pull_request:
push:
branches:
- main
- master
jobs:
Test:
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
os:
2022-02-14 09:50:58 +08:00
- windows-2022
2021-09-17 23:27:08 +08:00
- ubuntu-20.04
2022-02-14 09:50:58 +08:00
- macos-11
2021-09-17 23:27:08 +08:00
compiler:
- llvm
- gcc
2021-11-22 06:40:30 +08:00
# you can specify the version after `-` like `llvm-13.0.0` .
2021-11-23 15:51:10 +08:00
include:
2022-02-14 09:50:58 +08:00
- os: "windows-2022"
2021-11-23 15:51:10 +08:00
compiler: "msvc"
2021-09-17 23:27:08 +08:00
steps:
2022-01-23 08:56:54 +08:00
- uses: actions/checkout@v2
2021-11-23 15:51:10 +08:00
- name: Cache
uses: actions/cache@v2
with:
path: |
~/vcpkg
./build/vcpkg_installed
${{ env.HOME }}/.cache/vcpkg/archives
${{ env.XDG_CACHE_HOME }}/vcpkg/archives
${{ env.LOCALAPPDATA }}\vcpkg\archives
${{ env.APPDATA }}\vcpkg\archives
key: ${{ runner.os }}-${{ matrix.compiler }}-${{ env.BUILD_TYPE }}-${{ hashFiles('**/CMakeLists.txt') }}-${{ hashFiles('./vcpkg.json')}}
restore-keys: |
2022-02-21 07:55:32 +08:00
${{ runner.os }}-${{ env.BUILD_TYPE }}-
2021-11-23 15:51:10 +08:00
2021-09-17 23:27:08 +08:00
- name: Setup Cpp
2021-09-18 04:32:14 +08:00
uses: aminya/setup-cpp@v1
2021-09-17 23:27:08 +08:00
with:
compiler: ${{ matrix.compiler }}
2022-01-30 07:13:52 +08:00
vcvarsall: ${{ contains(matrix.os, 'windows') }}
2021-09-17 23:27:08 +08:00
cmake: true
ninja: true
2021-11-22 07:07:02 +08:00
vcpkg: true
2022-01-30 07:13:52 +08:00
cppcheck: true
clangtidy: true # instead of `true` , which chooses the default version, you can pass a specific version.
# ...
2021-09-17 23:27:08 +08:00
```
2022-01-30 07:13:52 +08:00
## Inside Docker
2021-09-19 00:50:18 +08:00
2021-11-22 04:20:51 +08:00
Here is an example for using setup_cpp to make a builder image that has the Cpp tools you need.
2021-09-19 00:50:18 +08:00
```dockerfile
2022-02-15 16:25:37 +08:00
FROM ubuntu:devel
2021-09-19 00:50:18 +08:00
2021-09-19 01:05:52 +08:00
# add setup_cpp
2021-09-19 00:50:18 +08:00
WORKDIR "/"
2021-09-19 01:35:33 +08:00
RUN apt-get update -qq
2022-01-20 08:00:12 +08:00
RUN apt-get install -y --no-install-recommends wget
2022-04-16 17:51:35 +08:00
RUN wget --no-verbose "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp_linux"
2021-09-19 01:05:52 +08:00
RUN chmod +x ./setup_cpp_linux
2021-09-19 00:50:18 +08:00
2021-12-11 20:29:28 +08:00
# install llvm, cmake, ninja, and ccache
RUN ./setup_cpp_linux --compiler llvm --cmake true --ninja true --ccache true
2021-09-19 00:50:18 +08:00
2022-03-12 09:48:28 +08:00
# activate cpp environment variables
2022-03-01 18:43:50 +08:00
RUN source ~/.cpprc
2022-01-18 10:51:14 +08:00
2021-09-30 08:56:28 +08:00
ENTRYPOINT [ "/bin/sh" ]
2021-09-19 00:50:18 +08:00
```
See [this folder ](https://github.com/aminya/setup-cpp/tree/master/building/docker ), for some dockerfile examples.
2021-09-19 01:05:52 +08:00
If you want to build the ones included, then run:
2021-09-19 00:50:18 +08:00
```ps1
2022-02-15 16:25:37 +08:00
docker build -f ./building/docker/ubuntu.dockerfile -t setup_cpp .
2021-09-19 00:50:18 +08:00
```
2022-01-30 07:13:52 +08:00
Where you should use the path to the dockerfile after `-f` .
2021-09-30 08:56:28 +08:00
After build, run the following to start an interactive shell in your container
```ps1
docker run -it setup_cpp
```
2021-12-07 05:02:01 +08:00
2022-01-30 07:13:52 +08:00
## Inside Docker inside GitHub Actions
2021-12-07 05:02:01 +08:00
You can use the docker file discussed in the previous section inside GitHub Actions like the following:
```yaml
jobs:
Docker:
runs-on: ${{ matrix.os }}
strategy:
matrix:
os:
- ubuntu-20.04
steps:
- uses: actions/checkout@v2
- name: Build
id: docker_build
run: |
docker build -f ./building/docker/debian.dockerfile -t setup_cpp .
env:
ACTIONS_ALLOW_UNSECURE_COMMANDS: true
2021-12-07 16:46:07 +08:00
```
2021-12-17 01:51:52 +08:00
2022-01-30 07:13:52 +08:00
## Inside GitLab pipelines
2022-01-20 09:42:18 +08:00
The following gives an example for setting up a C++ environment inside GitLab pipelines.
.gitlab-ci.yaml
```yaml
2022-02-15 16:25:37 +08:00
image: ubuntu:devel
2022-01-20 09:42:18 +08:00
stages:
- test
.setup_linux: & setup_linux |
DEBIAN_FRONTEND=noninteractive
# set time-zone
TZ=Canada/Pacific
ln -snf /usr/share/zoneinfo/$TZ /etc/localtime & & echo $TZ > /etc/timezone
# for downloading
apt-get update -qq
apt-get install -y --no-install-recommends curl gnupg ca-certificates
# keys used by apt
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3B4FE6ACC0B21F32
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1E9377A2BA9EF27F
.setup_cpp: & setup_cpp |
2022-04-16 17:51:35 +08:00
curl -LJO "https://github.com/aminya/setup-cpp/releases/download/v0.11.0/setup_cpp_linux"
2022-01-20 09:42:18 +08:00
chmod +x setup_cpp_linux
./setup_cpp_linux --compiler $compiler --cmake true --ninja true --ccache true --vcpkg true
2022-03-01 18:43:50 +08:00
source ~/.cpprc
2022-01-20 09:42:18 +08:00
.test: & test |
# Build and Test
# ...
test_linux_llvm:
stage: test
variables:
compiler: llvm
script:
- *setup_linux
- *setup_cpp
- *test
test_linux_gcc:
stage: test
variables:
compiler: gcc
script:
- *setup_linux
- *setup_cpp
- *test
```
2021-12-17 01:51:52 +08:00
# Articles
[Setup-Cpp on Dev.to ](https://dev.to/aminya/setup-cpp-3ia4 )
# Usage Examples
2022-01-30 07:13:52 +08:00
- [cpp-best-practices starter project ](https://github.com/cpp-best-practices/cpp_starter_project )
2021-12-17 01:51:52 +08:00
- [libclang ](https://github.com/atilaneves/libclang )
- [dpp ](https://github.com/atilaneves/dpp )
- [d-tree-sitter ](https://github.com/aminya/d-tree-sitter )
See all of the usage examples on GitHub [here ](https://github.com/search?q=aminya%2Fsetup-cpp+path%3A.github%2Fworkflows%2F+language%3AYAML+fork%3Atrue&type=code ).