You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since releasing the MVP of Orca for the Wheel Reinvention Jam, we've had a flurry of activity from the community - which has revealed lots of ways that we need to improve the Orca tooling in order to help people get started and make Orca work with more systems and languages.
The biggest themes we saw in the feedback were:
Difficulty building the runtime
Unclear boundaries between runtime and user apps
Python problems
With that in mind, here's our near-term roadmap for tooling improvements:
orca_install [--install-dir dir] : downloads and install orca tool in an install dir. This dir must be added to PATH.
orca_install then calls the orca tool with the update command, which downloads the latest binaries and wasm SDK and install them in the same directory as the tool.
Tool commands:
orca sdk-path [--version version] prints the path of the SDK (so that people can add the include/lib paths to their build commands)
orca bundle [--version version] [--target platform] [--resource-dir dir] [--resource file] [--icon icon] --name name module.wasm bundle wasm module and resources into an application. Support cross-bundling.
orca update [--install-dir dir] downloads and install the latest versions of the tool, binaries and SDK in the install dir.
The text was updated successfully, but these errors were encountered:
This was completed in a series of PRs (#55, #60, #62). Replacing python with a zig build script for the dev tooling can be explored later and is tracked by #25, so this issue can be closed.
Since releasing the MVP of Orca for the Wheel Reinvention Jam, we've had a flurry of activity from the community - which has revealed lots of ways that we need to improve the Orca tooling in order to help people get started and make Orca work with more systems and languages.
The biggest themes we saw in the feedback were:
With that in mind, here's our near-term roadmap for tooling improvements:
And later on:
Installation:
orca_install [--install-dir dir]: downloads and installorcatool in an install dir. This dir must be added to PATH.orca_installthen calls theorcatool with theupdatecommand, which downloads the latest binaries and wasm SDK and install them in the same directory as the tool.Tool commands:
orca sdk-path [--version version]prints the path of the SDK (so that people can add the include/lib paths to their build commands)orca bundle [--version version] [--target platform] [--resource-dir dir] [--resource file] [--icon icon] --name name module.wasmbundle wasm module and resources into an application. Support cross-bundling.orca update [--install-dir dir]downloads and install the latest versions of the tool, binaries and SDK in the install dir.The text was updated successfully, but these errors were encountered: