tutorials/editor/command_line_tutorial

[giscus[bot]]

tutorials/editor/command_line_tutorial

Some developers like using the command line extensively. Godot is designed to be friendly to them, so here are the steps for working entirely from the command line. Given the engine relies on almos...

https://docs.godotengine.org/en/latest/tutorials/editor/command_line_tutorial.html

[Minimata]

When using the Godot CLI to export a project, having the --import alongside the --export-release flag seems to be messing up autoloads called from GDScript in the release build.

I used to export like this:
godot --headless --verbose --build-solutions --import --export-release "Windows Desktop" path/to/exe

The export works fine but when launching the exported game with the console executable, I got the following error:

Parse Error: Identifier "SceneLoader" not declared in the current scope.

Other autoloads work fine (I use them for music and inputs) but the SceneLoader is the one I call in my GDScript, which raises the above issue. I'm not sure why I had --import here in the first place but it didn't raise any error before relying on autoloads in code.

Removing the --import fixed the issue since I didn't rely on it for the release export. Though if they're incompatible, I would expect an error from a failed export attempt or from the CLI itself warning me these two arguments aren't supposed to be used together. All I had here was an obscure and very unexpected error from specific autoloads which was undocumented anywhere and a pain to diagnose.

My mistake on fumbling the arguments around, but having an error or warning thrown by the CLI could help fumblers like myself in the future.

My windows export pipeline now looks like this, for anyone stumbling on this:

• godot --headless --editor --build-solutions --quit --import --path /path/to/project
• godot --headless --verbose --build-solutions --export-release "Windows Desktop" path/to/exe

[Calinou]

--export-* arguments always imply --import, so you don't need to specify it explicitly. The same goes for --quit, which is implied when using either --export-* or --import.

We should probably ignore --import in this case to avoid bugs.