The following intructions can be used to install .NET Core on Linux ARM64.
Pro tip: Check out .NET Core Docker files to determine the exact instructions for installing .NET Core builds, for example .NET Core 3.1 ARM32 SDK Dockerfile.
The following instructions install the latest .NET Core globally. It isn't required to do that, but it provides the best experience.
| #!/usr/bin/env python3 | |
| # let's say you have a C++ project in Nix that you want to work on with CLion so that the Nix dependencies are available | |
| # put this script in your project directory | |
| # then, in Settings -> Build, Execution, Deployment -> Toolchains set CMake to this script | |
| # if you need any extra nix-shell arguments, add them to the invocation at the bottom | |
| import os | |
| import sys | |
| import shlex |
| (ns byte | |
| "My own take on byte conversion. `(byte)` doesn't work with unsigneds | |
| within clojure, and signed values don't work well within | |
| clojurescript. Includes additional bitwise functions for working | |
| specifically with bytes.") | |
| (defn signed | |
| "Signed byte that works between clojure and clojurescript. |
| #include <sstream> | |
| #include <iostream> | |
| #include <iomanip> | |
| std::string uint8_to_hex_string(const uint8_t *v, const size_t s) { | |
| std::stringstream ss; | |
| ss << std::hex << std::setfill('0'); | |
| for (int i = 0; i < s; i++) { |
| /* | |
| * Self-Explanatory Protocol Buffer Lang Guide | |
| */ | |
| /* | |
| * Why Protocol Buffers? | |
| * Protocol buffers are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data – think XML, but smaller, faster, and simpler. | |
| * You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. | |
| * Protocol Buffers are Schema Of Messages. They are language agnostic. |
There are multiple ways to get a full disk encrypted arch linux system on raspberry. In this tutorial, we will install a 64-bit arch linux armv8 system, using dropbear as ssh server for remote pre-boot unlocking of the root filesystem. However, it will still be possible to unlock and use the pi as usual, with a keyboard and monitor. We will also create an unencrypted partition in the installation process, usable as a rescue system.
Differences to the 32-bit arch linux arm version:
Guillaume Papin(@Sarcasm) has a thorough article about compilation databases.
% mkdir build
% (cd build; cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=YES ..)
% ln -s build/compile_commands.json
| version: "3.5" | |
| services: | |
| mongo: | |
| image: mongo:latest | |
| container_name: mongo | |
| environment: | |
| MONGO_INITDB_ROOT_USERNAME: admin | |
| MONGO_INITDB_ROOT_PASSWORD: admin | |
| ports: |
