hasayakey hasayakey

Key Points

In general, binaries built just for x86 architecture will automatically be run in x86 mode
You can force apps in Rosetta 2 / x86 mode by right-clicking app, click Get Info, check "Open using Rosetta"
You can force command-line apps by prefixing with arch -x86_64, for example arch -x86_64 go
Running a shell in this mode means you don't have to prefix commands: arch -x86_64 zsh then go or whatever
Don't just immediately install Homebrew as usual. It should most likely be installed in x86 mode.

Homebrew

Not all toolchains and libraries properly support M1 arm64 chips just yet. Although

WWDC                                2006  2007  2008  2009
2010 2011 2012 2013 2014

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`)

Notation iOS 9

This homebrewed notation I typically use when evaluating secure boot designs of embedded devices. It doesn't apply accurately for the iOS review, hides the key-wrapping schema for example. But it's enough to keep track of storage location of secrets and some interdependency.

pfk                  = 256bit per_file_key

	defaults write com.apple.dt.Xcode ShowDVTDebugMenu -bool YES
	sudo mkdir -p /Applications/Xcode.app/Contents/Developer/AppleInternal/Library/Xcode
	sudo touch /Applications/Xcode.app/Contents/Developer/AppleInternal/Library/Xcode/AppleInternal.plist

	# Don't forget to restart Xcode

	# 2017-10-01T14:14:44+00:00

	108.175.32.0/20
	108.175.34.0/24
	108.175.35.0/24
	192.173.64.0/18
	198.38.100.0/24
	198.38.101.0/24
	198.38.108.0/24
	198.38.109.0/24

	Hi All!

	I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future.
	Feel free to request any features you'd like to see, and I'll prioritize them accordingly.
	One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it.

	Here's the link to the repository: https://github.com/Pulimet/ADBugger

	App Description:
	ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups.

	var readline = require('readline'),
	fs = require('fs');

	var LinkMap = function(filePath) {
	this.files = []
	this.filePath = filePath
	}

	LinkMap.prototype = {
	start: function(cb) {

	#!/bin/bash

	# Size at the end is * 2048 where 2048 = 1 MB, so 1572864 = 768 MB
	#DISK=`/usr/bin/hdiutil attach -nobrowse -nomount ram://1572864`
	DISK=`/usr/bin/hdiutil attach -nobrowse -nomount ram://2097152`

	/usr/sbin/diskutil erasevolume HFS+ "RamDiskCache" $DISK

	CACHEDIR="/Volumes/RamDiskCache/$USER"

	i386 : iPhone Simulator
	x86_64 : iPhone Simulator
	arm64 : iPhone Simulator
	iPhone1,1 : iPhone
	iPhone1,2 : iPhone 3G
	iPhone2,1 : iPhone 3GS
	iPhone3,1 : iPhone 4
	iPhone3,2 : iPhone 4 GSM Rev A
	iPhone3,3 : iPhone 4 CDMA
	iPhone4,1 : iPhone 4S