bjoli/BjoManual
SHA256
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Getting started says where Bjolang is: the repository, built from source

Browse source 
There are no releases, so the section now says so, and gives the clone and
the build in the order Compiling.org has them: the runtime, the compiler,
the standard library. Updating is a pull and bjo rebjo. The editor support
paragraph links the repository it mentions.

🤖 Generated with [ECA](https://eca.dev) (anthropic/claude-opus-5-5)

Co-Authored-By: eca-agent <git@eca.dev>
This commit is contained in:
Linus Björnstam 2026-10-01 21:23:38 +02:00
parent 8eb1bd3df6
commit d35a116b8a
1 changed files with 22 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

24
_01.Language-basics.sz
View file

@ -1,6 +1,26 @@
@section{Getting started}
Bjolang needs only two things: dotnet 10 and an f# compiler. Once those are installed you build the compiler using dotnet build -c Release, run ./build_std.sh and ./run_tests.py and ./run_bjo_tests.py in the main directory. Then you can use the bjo executable in the bjo directory. Personally I alias a shell command to the path of bjo, since there currently is no way to install it properly.
Bjolang is only installed from source. There are no releases or packages: you clone the repository at @link["https://github.com/bjoli/Bjolang"]{github.com/bjoli/Bjolang} and build it where it is.
It needs only two things: dotnet 10 and an f# compiler. The .NET 10 SDK comes with both. Once that is installed, clone the repository and build the runtime, the compiler and the standard library:
@codeblock[#:lang "text"]|{
git clone https://github.com/bjoli/Bjolang
cd Bjolang
dotnet build BjolangRuntime/BjolangRuntime.csproj -c Release
dotnet build -c Release
./build_std.sh
}|
If you want to make sure everything works, run @code{./run_tests.py} and @code{./run_bjo_tests.py} in the same directory. Then you can use the bjo executable in the bjo directory: @code{./bjo/bjo run hello.bjo}. Personally I alias a shell command to the path of bjo, since there currently is no way to install it properly. Compiled programs find the standard library in the directory you built it in, so leave the checkout where it is.
To update, pull and build again:
@codeblock[#:lang "text"]|{
git pull
./bjo/bjo rebjo
./build_std.sh
}|
@subsection{Your first bjolang program}
@ -61,7 +81,7 @@ This can then be destructed using pattern matching.
@subsubsection{Editor support}
Bjolang was written in emacs, and emacs is currently the only editor with limited bjolang support through the file bjomode.el in the main github repository. It lacks any fancy things, but handles a modicum of indentation and syntax highlighting.
Bjolang was written in emacs, and emacs is currently the only editor with limited bjolang support through the file bjomode.el in the @link["https://github.com/bjoli/Bjolang"]{main github repository}. It lacks any fancy things, but handles a modicum of indentation and syntax highlighting.
@subsection{Values, types and signatures}