agentleFS
SentryKnown publishergetsentry/sentry-unreal/.claude/skills/build-deps/SKILL.md

build-deps

Skill177 starsChanged 4 days agoMITView on GitHub

Build plugin SDK dependencies locally and refresh ThirdParty binaries

  • Deletes or force-pushes

The file

Files
SKILL.md

Build plugin dependencies from local SDK checkouts and replace the pre-built binaries under plugin-dev/Source/ThirdParty/. Use when testing unreleased SDK changes.

Steps

1. Select dependencies to build

Determine which dependencies to build from conversation context:

DependencyFlagPath parameterEnv var fallbackNotes
sentry-native-Native-NativePathSENTRY_NATIVE_PATHBuilds for host platform: Windows/Linux (Crashpad + Native backends), macOS (Native backend)
sentry-cocoa-Cocoa-CocoaPathSENTRY_COCOA_PATHmacOS host only; produces iOS + Mac artifacts
sentry-java-Java-JavaPathSENTRY_JAVA_PATHGradle build; also downloads the matching sentry-native NDK release
crash reporter-CrashReporter-CrashReporterPathSENTRY_CRASH_REPORTER_PATH.NET build for host platform

-All builds everything supported on the host platform.

2. Verify source paths

For each selected dependency, check that its env var is set (verify non-empty only, never print values; on Windows use [System.Environment]::GetEnvironmentVariable('VAR_NAME')) or that an explicit path parameter was provided. If missing, ask the user for the repository path and pass it via the corresponding path parameter.

3. Run the build

Execute from the repo root:

pwsh ./scripts/build-deps.ps1 -All                                        # everything for host platform
pwsh ./scripts/build-deps.ps1 -Cocoa -Java                                # specific SDKs
pwsh ./scripts/build-deps.ps1 -Native -NativePath "/path/to/sentry-native" # explicit source path

The build can take longer than the default command timeout — run it in the background and monitor its output, or raise the timeout accordingly.

4. Clean stale build artifacts

UnrealBuildTool does not reliably detect ThirdParty binary changes, so after a successful deps rebuild remove the plugin Binaries/Intermediate directories to avoid linking against stale binaries:

REPO=$(git rev-parse --show-toplevel)
rm -rf "$REPO/plugin-dev/Binaries" "$REPO/plugin-dev/Intermediate"

sample/Plugins/sentry is a symlink to plugin-dev, so the plugin artifacts live in plugin-dev/ itself.

5. Rebuild the project

Suggest running /ue-build so the project is recompiled against the freshly built dependencies.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.