| <div id="root"></div> |
| <div id="root"></div> |
| <div id="root"></div> |
| <div id="root"></div> |
| ./configure --prefix=/home/pi/.local --with-sound=yes --with-x-toolkit=yes --with-wide-int --with-cairo --with-modules --with-mailutils --with-x | |
| sudo apt-get update | |
| sudo apt install \ | |
| libx11-dev \ | |
| libtiff-dev \ | |
| libgtk2.0-dev \ | |
| libncurses-dev \ | |
| mailutils-imap4d \ |
| { stdenv, fetchurl, makeWrapper, buildFHSUserEnv }: | |
| let | |
| fhsEnv = buildFHSUserEnv { | |
| name = "esp8266-toolchain-env"; | |
| targetPkgs = pkgs: with pkgs; [ zlib ]; | |
| runScript = ""; | |
| }; | |
| in |
| { nixpkgs ? import <nixpkgs> {} }: | |
| let | |
| inherit (nixpkgs) pkgs; | |
| in | |
| pkgs.stdenv.mkDerivation { | |
| name = "esp8266-env"; | |
| buildInputs = with pkgs; [ | |
| gawk gperf gettext automake bison flex texinfo help2man libtool autoconf ncurses5 cmake |
| { stdenv, fetchurl, makeWrapper, buildFHSUserEnv }: | |
| let | |
| fhsEnv = buildFHSUserEnv { | |
| name = "esp32-toolchain-env"; | |
| targetPkgs = pkgs: with pkgs; [ zlib ]; | |
| runScript = ""; | |
| }; | |
| in |
| { nixpkgs ? import <nixpkgs> {} }: | |
| let | |
| inherit (nixpkgs) pkgs; | |
| in | |
| pkgs.stdenv.mkDerivation { | |
| name = "esp-idf-env"; | |
| buildInputs = with pkgs; [ | |
| cmake gawk gperf gettext automake bison flex texinfo help2man libtool autoconf ncurses5 cmake |
I've been working on a talk about the virtues of building toy examples for the purpose of communicating ideas with simple interactive examples.
The toys I talk about in my presentation are based my interest in tools that allow programmers to quickly build web applications that allow them to explore their architecture. So to kickstart this series off, I want to introduce a simple
