Bryan Woods bwoods

What we want to do

Lets say we have a library that is part of a larger CMake project, and we want to seperate it out so it can be used in more projects. For the sake of convenience lets say it is already largely seperate from the parent project, i.e. in its own directory with a CMakeLists.txt, and referenced with add_subdirectory from the parent project.

In order to fully seperate it we need to:

Make it buildable on its own. If it has depencies, it needs to use find_package itself to find them. If it has

Mixed Markdown and Shell Scripting

: By the power of this magic string: ex: set ft=markdown ;:<<'```shell' #, this file is now both a markdown document and an executable shell script. chmod +x it and try running it!

The above line does just what it says. More specifically, when placed within in the first 5 lines and preceded only by blank lines or #-prefixed markdown headers:

The first part of the magic string makes github and various editors (e.g. atom with the vim-modeline packge) treat the file as having markdown syntax (even if the file doesn't have an extension)
The second part (if run in a shell), makes the shell skip execution until it encounters the next ```shell block.

(The line also has to start with a : so that it's valid shell code.)

Build settings reference

Active Build Action (`ACTION`)

A string identifying the build system action being performed.

Additional SDKs (`ADDITIONAL_SDKS`)

The locations of any sparse SDKs that should be layered on top of the one specified by Base SDK (SDKROOT). If more than one SDK is listed, the first one has highest precedence. Every SDK specified in this setting should be a "sparse" SDK, for example, not an SDK for an entire macOS release.

Alternate Install Group (`ALTERNATE_GROUP`)

Swift Ownership Manifesto TL;DR

Most of the manifesto is background and detailed definitions -- if you're confused or want details, read the manifesto!

https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170213/032155.html

Note also that manifestos aren't complete proposals -- syntax and details may change!

One piece of background: inout is kinda complicated because it can be used on computed properties -- foo(&val.x) might be sugar for

Simple: Fixed Delta Time

let mut t: 0.0;
let dt = 1.0 / 60.0;

loop {
    update(t, dt);
    render();

	#!/bin/bash
	#
	# Install specific version of a Homebrew formula
	#
	# Usage: brewv.sh formula_name desired_version
	#
	# Notes:
	# - this will unshallow your brew repo copy. It might take some time the first time
	# you call this script
	# - it will uninstall (instead of unlink) all your other versions of the formula.

	/*
	* Copyright (c) 2020-present Daniel Trugman
	*
	* Permission is hereby granted, free of charge, to any person obtaining a copy
	* of this software and associated documentation files (the "Software"), to deal
	* in the Software without restriction, including without limitation the rights
	* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	* copies of the Software, and to permit persons to whom the Software is
	* furnished to do so, subject to the following conditions:
	*

	///$(which true);FLAGS="-g -Wall -Wextra --std=c17 -O1 -fsanitize=address,undefined";THIS_FILE="$(cd "$(dirname "$0")"; pwd -P)/$(basename "$0")";OUT_FILE="/tmp/build-cache/$THIS_FILE";mkdir -p "$(dirname "$OUT_FILE")";test "$THIS_FILE" -ot "$OUT_FILE" \|\| $(which clang \|\| which gcc) $FLAGS "$THIS_FILE" -o "$OUT_FILE" \|\| exit $?;exec bash -c "exec -a \"$0\" \"$OUT_FILE\" $([ $# -eq 0 ] \|\| printf ' "%s"' "$@")"
	#include <stdio.h>

	int main() {
	printf("Hello world!\n");
	return 0;
	}

	# This CMake file will build Freetype and Harfbuzz as external
	# projects. We follow the build description as described here:
	# https://sourceforge.net/projects/freetype/files/freetype2/2.5.3/ So,
	# first we build Freetype2 w/o Harfbuzz, then we build Harfbuzz with
	# freetype support after which we rebuild Freetype2 again.
	#
	# Both CMake files of Freetype2 and Harfbuzz are depending on
	# pkg-config to find the dependencies for both projects. I've
	# included a patch for Freetype2 and Harfbuzz which allows you to
	# build Freetype2 and Harbuzz with pure CMake features. So I removed

	# On OS X, with an ffmpeg installed via Homebrew, the following command works and results in a single-frame movie file that is compatible with Chrome, QuickTime and the latest iDevices:
	ffmpeg -i FILENAME.png -an -vcodec libx264 -coder 1 -flags +loop -cmp +chroma -subq 10 -qcomp 0.6 -qmin 10 -qmax 51 -qdiff 4 -profile:v high -level 4.2 -pix_fmt yuv420p -vf “scale=trunc(iw/2)2:trunc(ih/2)2” -trellis 2 -partitions +parti8x8+parti4x4 -crf 24 -threads 0 -r 25 -g 25 -y FILENAME.mp4