Clone glassechidna's zxing-cpp fork.
In CMakeLists.txt
, add include(toolchain.cmake)
as the first line.
Create a new file, toolchain.cmake
:
set(CMAKE_SYSTEM_NAME Linux)
#!/bin/bash | |
# Print a message and kill the script. | |
die() { | |
echo "$@" 1>&2 | |
exit 1 | |
} | |
# Finds the top of the repo. | |
find_git_repo_top() { |
FROM tensorflow/tensorflow:2.9.1 | |
LABEL description="Magenta 2.14.0 on Tensorflow 2.9.1" | |
USER root | |
RUN apt-get update --fix-missing && \ | |
apt-get -y install expect build-essential libasound2-dev libjack-dev git-core ffmpeg vim | |
ENV MC_REMOTE="https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh" | |
ENV MC_LOCAL="/tmp/miniconda-install.sh" | |
ENV CONDA_PATH="/root/miniconda3" |
fun ConnectivityManager.observeAdapterConnectivity(): Flow<Boolean> { | |
return callbackFlow { | |
val callback = object: ConnectivityManager.NetworkCallback() { | |
override fun onAvailable(network: Network) { | |
trySendBlocking(true) | |
} | |
override fun onLost(network: Network) { | |
trySendBlocking(false) | |
} |
Clone glassechidna's zxing-cpp fork.
In CMakeLists.txt
, add include(toolchain.cmake)
as the first line.
Create a new file, toolchain.cmake
:
set(CMAKE_SYSTEM_NAME Linux)
The Amplify tools create a lot of resources in your AWS account. When you stop using Amplify, you'll want some way to remove it all. This document discusses some various strategies to cleanup your AWS account when offboarding Amplify.
The commands below will call the AWS CLI (and not the Amplify CLI.)
Fortunately, most of the Amplify stack if managed through CloudFormation under the hood. This means that you can cleanup most of the outputs just by deleting the Amplify "app."
A collection of some seminal pieces of customer feedback.
Regarding production-readiness:
Regarding contributions:
The V2 AWS Java SDK can be used from Android, with a few caveats.
Note: currently, this is limited to API 26 and higher (60% of production devices, as of 06JUL2020.)
Other Note: this document is not production guidance for application builders. These are some of my personal notes after some study and expirementation.
This document describes howto setup an AppSync endpoint, and talk to it using the Apollo Android 2.2.0 client.
In the AWS AppSync console, I created a new endpoint here, by selecting the "Event app" under "Start from a sample project."
The goal of this exercise is to show how a simple functional interface could be used to return a Result
value type. The Result
value type can contain an error (getError()
), or a value (getValue()
), depending. A user is able to figure this out by inspecting the Result.Type
, and exhausting the potential values of this enum via a switch
.
Consuming a multi-values result type:
package com.amplifyframework.ioscbs;
import android.app.Activity;
import android.os.Bundle;
import android.util.Log;