Skip to content

Conversation

@sensei-hacker
Copy link
Member

No description provided.

The SITL feature was broken because the code looked for binaries in
the wrong location. The path used __dirname which points to the Vite
build output (.vite/build/), but SITL binaries are in resources/public/sitl/.

Changes:
- Add getSitlBasePath() function that returns correct path based on
  whether app is packaged (process.resourcesPath) or in dev mode
  (app.getAppPath()/resources/public/sitl)
- Add extraResource in forge.config.js to include SITL in packages
- Add afterCopy hook to remove binaries for other platforms/architectures,
  reducing package size
The SITL feature was broken because the code looked for binaries in
the wrong location. The path used __dirname which points to the Vite
build output (.vite/build/), but SITL binaries are in resources/public/sitl/.

Changes:
- Add getSitlBasePath() function that returns correct path based on
  whether app is packaged (process.resourcesPath) or in dev mode
  (app.getAppPath()/resources/public/sitl)
- Add extraResource in forge.config.js to include SITL in packages
- Add afterCopy hook to remove binaries for other platforms/architectures,
  reducing package size
Fix SITL remove wrong architecture
Fix SITL binary path resolution for dev and packaged modes
@sensei-hacker sensei-hacker changed the title Build fixes from master to maintenance-9.x Merge build fix from master to maintenance-9.x Dec 24, 2025
@sensei-hacker sensei-hacker merged commit 3b32d36 into maintenance-9.x Dec 24, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants