soundyogi

# Windows
Build MyProjectEditor Win64 Development "D:\Unreal\MyProject\MyProject.uproject" -waitmutex

# Linux
Build.sh MyProjectEditor Linux Development "/home/mvlabat/unreal/projects/MyProject/MyProject.uproject" -waitmutex

soundyogi

:: Build client
RunUAT BuildCookRun -project="full_path.uproject"^
 -noP4 -platform=Win64^
 -clientconfig=Development -serverconfig=Development^
 -cook -allmaps -build -stage^
 -pak -archive -archivedirectory="Output Directory"

:: Cook client
RunUAT BuildCookRun -project="full_project_path_and_project_name".uproject^
 -noP4 -platform=Win64^

soundyogi

The solution I'm using is the following:

Compile the plugin using the command line:

"ENGINE_DIR\UE_4.22\Engine\Build\BatchFiles\RunUAT.bat" BuildPlugin -Plugin="PATH_TO_MY_PLUGIN\MyPlugin.uplugin" -Package="PATH_TO_BUILD_FOLDER" -TargetPlatforms=Win64 -Rocket -precompile

Obviously replace ENGINE_DIR, PATH_TO_MY_PLUGIN, MyPlugin, PATH_TO_BUILD_FOLDER

Note that you should either add -precompile to the argument (as above) or put bPrecompile=true into your build.cs files

soundyogi

Generations
The most important factor that differentiates CSS-in-JS libraries is how dynamic they are. By that we mean whether a CSS-in-JS library can use JavaScript variables in its templates, and — if so — to what scope of variables those templates have access to? Module scope? Component scope? Or maybe .render() method scope?

Below we define five generations of CSS-in-JS libraries based on their template dynamicity and whether they use inline styles or inject actual CSS; starting from generation one — for the most static libraries — and going all the way up to generation five. Although not strictly true, this also corresponds to how React styling libraries evolved over time.

1st Generation
First generation React styling libraries don't allow you to write styling in JavaScript and use any of JavaScript variables, instead, you have to use CSS pre-processors. The CSS source files are usually located in separate .*css files.

Notable example: css-modules
2nd Generation

soundyogi

Host Your Site Under Your Domain on IPFS

This is a step-by-step tutorial for hosting your website under your domain on IPFS, from zero, on a DigitalOcean Ubuntu 16.04.3 x64 Droplet (i am using the $10 variant with 2GB RAM).

Install IPFS

Log in as root.

First, make sure the system is up to date, and install tar and wget:

soundyogi

#!/bin/bash

function print_green {
  echo -e "\e[32m${1}\e[0m"
}

print_green 'Start'
 
print_green 'Cleanup log files'
find /var/log -type f | while read f; do echo -ne '' > $f; done

soundyogi

#!/bin/bash

sudo apt install build-essential checkinstall
sudo apt-get install libreadline-gplv2-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev

sudo apt install python2.7

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash

git clone https://github.com/c9/core.git c9sdk

soundyogi

/* global web3 */
import React from 'react';
import { DrizzleContext } from "drizzle-react";
import { drizzleProviderFactory } from '../../Provider';


type IDrizzleContext = {
  drizzle: object
  drizzleState: object
  initialized: boolean

soundyogi

/* global window */

// originally from: https://github.com/adrianmcli
// adapted by me

import Web3 from 'web3'


const fallback = 'wss://mainnet.infura.io/ws'

soundyogi

#vm machine needs nodejs
#download sdk
wget http://dl.google.com/android/android-sdk_r24.2-linux.tgz
tar -xvf android-sdk_r24.2-linux.tgz
rm android-sdk_r24.2-linux.tgz
mv android-sdk-linux/ android
#install essential sdk components
~/workspace/android/tools/android update sdk -u --all --filter 2,4,168
#install enviroment dependencies
sudo apt-get install lib32stdc++6