Building from the Command Line Interface (CLI)
You don’t need to build the whole of a SpatialOS project at the same time. What you build depends on what changes you’ve made to it:
If you’ve changed the schema
1. Build schema changes
Generate code from the schema:
Fix any code references that are broken by the schema changes.
spatial worker build <worker type>for any relevant workers.
You can then use your IDE to modify your code that uses the generated code.
2. Migrate the initial snapshot
If you change the schema, you’ll need to migrate your initial snapshot to the new schema, or generate a new one.
If you’ve changed worker code
1. Build worker code
When you’ve made a change to the code of your worker, run
spatial worker build <worker type>.
This runs the ‘build’ task for the worker, which normally puts the resulting assets within
See build configuration for details.
2. Update the initial snapshot
You must update your initial snapshot (or generate a new one) if you make any changes that affect what’s in the snapshot. This includes (but isn’t limited to):
- adding or removing entities in the initial state (by changing the code which adds them)
- changing the number of entities in the initial state (by changing the code which adds them)
- changing the template (used to spawn an entity) of any entity that’s in the initial snapshot, including
- adding components to the entity
- removing components from the entity
To clean the whole project, run
spatial worker clean.
This also removes the
build directory at the root of your project.
Building workers offline
You can use
spatial worker build to build workers offline, so you can iterate on local projects without an internet connection. For more information, see Using the SpatialOS CLI offline for local projects.