@squiggle.sh/cli-darwin-arm64 0.1.0 → 0.2.0

package/install-macos-agent.sh

@@ -0,0 +1,62 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+TARGET="${1:-}"
+if [ -z "$TARGET" ] || [ ! -d "$TARGET" ]; then
+  echo "usage: install-macos-agent.sh <path to your macos app target dir>" >&2
+  echo "  e.g. install-macos-agent.sh macos/MyApp-macOS" >&2
+  exit 2
+fi
+
+HERE="$(cd "$(dirname "$0")" && pwd)"
+DYLIB="$HERE/libsquiggleagent-mac.dylib"
+if [ ! -f "$DYLIB" ]; then
+  echo "libsquiggleagent-mac.dylib is not beside this script ($HERE)." >&2
+  echo "It ships in the squiggle CLI's platform package; reinstall squiggle-cli." >&2
+  exit 1
+fi
+
+DEST_DIR="$TARGET/Squiggle"
+mkdir -p "$DEST_DIR"
+cp "$DYLIB" "$DEST_DIR/libsquiggleagent-mac.dylib"
+echo "✓ copied libsquiggleagent-mac.dylib → $DEST_DIR/"
+
+cat <<'STEPS'
+
+Two steps left, in Xcode — they edit the project file, so they are yours to make:
+
+  1. Add a **Copy Files** build phase to the macOS app target:
+       Destination: Frameworks
+       Add:         Squiggle/libsquiggleagent-mac.dylib
+       ✅ Code Sign On Copy
+     Xcode signs it with the app's own identity, inside-out, at no cost. Without
+     this the dylib is not in the bundle and step 2 finds nothing to open.
+
+  2. Load it from the app, in AppDelegate.mm (or .swift), Debug only:
+
+       #if DEBUG
+       #import <dlfcn.h>
+       // …inside applicationDidFinishLaunching:
+       {
+         NSString *override = NSProcessInfo.processInfo.environment[@"SQUIGGLE_AGENT_DYLIB"];
+         NSString *bundled = [[NSBundle mainBundle] pathForResource:@"libsquiggleagent-mac"
+                                                             ofType:@"dylib"
+                                                        inDirectory:@"../Frameworks"];
+         NSString *path = override.length ? override : bundled;
+         if (path && !dlopen(path.fileSystemRepresentation, RTLD_NOW)) {
+           NSLog(@"[squiggle] agent dylib failed to load: %s", dlerror());
+         }
+       }
+       #endif
+
+     `SQUIGGLE_AGENT_DYLIB` is what `squiggle up` sets when it launches the app,
+     so honouring it first is what lets the CLI hand your app a freshly built
+     agent instead of whatever was bundled.
+
+Then:  squiggle up <your.bundle.id> --platform macos
+It prints the injected dylib's Mach-O UUID, which is the proof it is in.
+
+After you update Squiggle, run this script again and rebuild. A launch from the
+Dock, Finder or Xcode loads the copy bundled in the app, and that copy stays the
+version you installed; `squiggle doctor` flags it when it no longer matches.
+STEPS

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@squiggle.sh/cli-darwin-arm64",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Squiggle CLI binary for darwin-arm64 — installed automatically by @squiggle.sh/cli",
   "homepage": "https://squiggle.sh",
   "os": [
@@ -15,6 +15,8 @@
     "yuku-parser.node",
     "squiggle-host",
     "libsquiggleagent.dylib",
+    "libsquiggleagent-mac.dylib",
+    "install-macos-agent.sh",
     "LICENSE.md",
     "THIRD-PARTY-NOTICES.md"
   ],

package/squiggle

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/squiggle
-size: 65229632 bytes
-sha256: add4aac9149dfd22de4d455eb87da094dee7506a0f4f3b953e525bb6b266da98
+size: 65689280 bytes
+sha256: 757432d88fa34f889736014ced1d591767e43cb030e395d4ee0716a47e0c9523