When using SonarQube or SonarCloud to analyze a C/C++/Objective-C project, the Build Wrapper is a required component that is executed as a prefix to the build command. After the build has finished, a build-wrapper-dump.json file is generated in the Build Wrapper output directory. This file contains absolute file paths (source files, standard headers, libraries, etc…) which SonarScanner needs access to while running. On account of this, both the Build Wrapper and SonarScanner binaries must run on the same host.
In Azure Pipelines, there are some special scenarios where we may want to run them on different hosts:
The Azure Storage Client Library for C++ allows building applications against Microsoft Azure Storage. It supports both Windows and Linux platforms and has many dependencies during install. Therefore, it’s recommended to use a cross-platform library manager to install it.
In this post, we’ll learn about how to integrate the Azure Storage Client Library, which is installed via vcpkg, to a CMake project targeting both Windows and Linux platforms.
To secure web servers, an SSL certificate can be used to encrypt web traffic. It’s easy to create self-signed certificates as I’ve mentioned in the “Creating an HTTPS Server with Node.js using a Self-Signed Certificate” post but they’re not considered trusted by many applications. So in this post, we’re going to talk about:
Let’s have a look at the following examples to understand why GlobalSign has warned us about the dangers of self-signed certificates.
If you have a Node.js web server running over HTTP, you may want to enable HTTPS so that data exchanged over network is encrypted. To do this, you need an SSL certificate. In this post, we’re going to talk about how to generate a self-signed certificate in two different ways:
If you’re not familiar with public keys, private keys and SSL certificates, this post provides an excellent explanation about them.
pem is an npm package that allows easily creating self-signed certificates…
How we used WebRTC and a web browser to view remote content from an Electron service running on the cloud.
In this post, I’ll share how we built a simple HTML page that can connect to the Electron service mentioned in Streaming Electron for Fun and Profit post. If you haven’t read that one yet, please spend some time reading it first.
The jewel is in the lotus.