docs / guide / The Cajeta Guide
Chapters — 2. Kick the tires
- Introduction
- 0. Introduction
- 1. Installation
- 2. Kick the tires
- 3. Your first project
- 4. Running your application
- 5. Debugging
- 6. Keywords
- 7. Comments
- 8. Native types
- 9. Type kinds
- 10. Allocation
- 11. Ownership & borrowing
- 12. Control flow
- 13. Strings & formatting
- 14. Templates & wildcards
- 15. Lambdas & captures
- 16. Operator overloading
- 17. Inheritance
- 18. Annotations & synthesis
- 19. DI & aspects
- 20. Error handling
- 21. Reflection
- 22. Differentiation
- 23. Code coverage
- 23. Profiling
- 24. Notebooks
- 25. Writing XPU Kernels
02 — Kick the tires
Four steps to prove the install works: check the version, scaffold hello world, compile it to an executable, run it.
1. Check the install
$ cajeta --version
cajeta 0.8.0 (8190ee59)
A version string means the toolchain is on your PATH and healthy.
2. Create hello world
$ cajeta init basic hello
Initialized 'basic' archetype in hello:
cajeta.json
src/main/cajeta/com/example/basic/Main.cajeta
$ cd hello
3. Compile to an executable
$ cajeta build
Task 'build' outputs:
path = build/exe/com.example.basic
sha256 = sha256:...
The output is a native binary.
4. Run it
$ ./build/exe/com.example.basic
hello from com.example.basic
That’s the whole loop: init → build → run. Everything else — what the
manifest means, the other project types, the rest of the cajeta command —
comes next.
Next: Your first project.