GeroHerkenrath

/// This file contains some helper properies, functions, and types that make writing other scripts a lot easier.
/// Put this and the related `rebuildBinaries.swift` file into a folder named "ScriptHelper" on the same level as
/// the scripts or adapt the paths below accordingly.
///
/// To then use the helper in a Swift script you need to do three things:
/// 1. Compile it into an importable module
/// 2. Make it visible and linkable to your script and import it in its code
///
/// For the first point there is a helper script provided, see `rebuildBinaries.swift`. It's also a Swift script,
/// but does not depend on these helpers. Used as is it compiles the module into a `bin` folder and simply names

pookjw

@available(iOS 15.0, *)
public struct RichTextEditor : SwiftUICore.View {
  public init(text: SwiftUICore.Binding<Foundation.AttributedString>)
  @_Concurrency.MainActor @preconcurrency public var body: some SwiftUICore.View {
    get
  }
  @available(iOS 15.0, *)
  public typealias Body = @_opaqueReturnTypeOf("$s7SwiftUI14RichTextEditorV4bodyQrvp", 0) __
}
@available(*, unavailable)

stephancasas

//
//  DumbHTTPServer.swift
//  DumbHTTPServer
//
//  Created by Stephan Casas on 3/29/24.
//

import SwiftUI;
import Combine;

saagarjha

// To compile: clang++ -arch x86_64 -arch arm64 -std=c++20 library_injector.cpp -lbsm -lEndpointSecurity -o library_injector,
// then codesign with com.apple.developer.endpoint-security.client and run the
// program as root.

#include <EndpointSecurity/EndpointSecurity.h>
#include <algorithm>
#include <array>
#include <bsm/libbsm.h>
#include <cstddef>
#include <cstdint>

saagarjha

// To compile: clang stop_at_entry.c -lbsm -lEndpointSecurity -o stop_at_entry,
// then codesign with com.apple.developer.endpoint-security.client and run the
// program as root.

#include <EndpointSecurity/EndpointSecurity.h>
#include <assert.h>
#include <bsm/libbsm.h>
#include <dispatch/dispatch.h>
#include <signal.h>
#include <stdbool.h>

burke

# typed: true
# frozen_string_literal: true
require('dev')
require('fileutils')

module Dev
  module Helpers
    class APFSVolume
      extend(T::Sig)

kastiglione

Debugging the Swift Toolchain

Use these steps to debug components of the Swift toolchain. This allows you to see Swift's source code from the debugger – instead of disassembly. The debugger can also provide some variable names and values. This has been initially tested with libswiftCore.dylib.

These instructions were updated as of Swift 5.2.1.

Prerequisites

burke

# typed: false
# frozen_string_literal: true

# Note: This is loaded *ludicrously* early in the boot process: please don't
# introduce other dependencies here.

# ===

# Okay so here's the deal. When we compile a bundle of ruby code via
# `bundlerEnv`, we install all the gems individually into a bunch of separate

kastiglione

Recently, we wanted call swift-demangle from code, but calling out to the process frequently was a bit too slow, and meant parsing the output of -tree-only, since we wanted to access module and class names, for example.

Fortunately there's libswiftDemangle.dylib for this, but it's a C++ API. Compiling against it requires #includeing headers from both Swift and LLVM.

Using CMake, both Swift and LLVM can easily be added as dependencies, but we build this project with SwiftPM. To build with SwiftPM, we imported the necessary headers. Roughly, here are the steps to determine which specific Swift

Omar-Ikram

//
//  main.m
//  EndpointSecurityDemo
//
//  Created by Omar Ikram on 17/06/2019 - macOS Catalina 10.15 Beta 1 (19A471t)
//  Updated by Omar Ikram on 15/08/2019 - macOS Catalina 10.15 Beta 5 (19A526h)
//  Updated by Omar Ikram on 01/12/2019 - macOS Catalina 10.15 (19A583)
//  Updated by Omar Ikram on 31/01/2021 - macOS Big Sur 11.1 (20C69)
//  Updated by Omar Ikram on 07/05/2021 - macOS Big Sur 11.3.1 (20E241)
//  Updated by Omar Ikram on 04/07/2021 - macOS Monterey 12 Beta 2 (21A5268h)