@@ -33,7 +33,7 @@ your development elsewhere, if you like, and make a symbolic link.
34+ git fetch
34+ git fetch
35+ git checkout <branch> # optional
35+ git checkout <branch> # optional
36−+ scripts/bootstrap
36++ sh/bootstrap
38+ git clone https://github.com/urbit/arvo
38+ git clone https://github.com/urbit/arvo
@@ -66,9 +66,9 @@ If this describes your task, read this section. If not, skip to the next sectio
66 + rm -rf urbit
66 + rm -rf urbit
67 + git clone https://github.com/<yourname>/urbit
67 + git clone https://github.com/<yourname>/urbit
68 + cd urbit
68 + cd urbit
69− + scripts/bootstrap
69+ + sh/bootstrap
70 + verify that the new submodule is present
70 + verify that the new submodule is present
71− + scripts/build
71+ + sh/build
72 + verify that the urbit executable is built and linked to the new library
72 + verify that the urbit executable is built and linked to the new library
73+ submit a pull request from your copy of <libsquareroots> to the urbit copy
73+ submit a pull request from your copy of <libsquareroots> to the urbit copy
74+ submit a pull request from your copy of urbit to the urbit copy
74+ submit a pull request from your copy of urbit to the urbit copy
@@ -632,7 +632,7 @@ You've edited C code; now you need to compile it to build a new urbit executable
632 + meson configure -Dbuildtype=debug build
632 + meson configure -Dbuildtype=debug build
634 Note that debugoptimized builds run slower than release builds, and debug builds run slower yet. Booting a debug builkd of urbit may take several minutes. [ N.B. compiler flags -O2 vs -O3 ]
634 Note that debugoptimized builds run slower than release builds, and debug builds run slower yet. Booting a debug builkd of urbit may take several minutes. [ N.B. compiler flags -O2 vs -O3 ]
635−+ scripts/build
635++ sh/build
637## Compile the Hoon code into a pill
637## Compile the Hoon code into a pill
@@ -754,7 +754,7 @@ It would be convenient to fire up a second urbit in a terminal next to your fake
754Then you can run identical commands in each, in parallel, and confirm that they do the same thing.
754Then you can run identical commands in each, in parallel, and confirm that they do the same thing.
756+ edit ~/tlon/urbit/jets/e/secp.c (or whatever) to include `fprintf(stderr, "*** u3we_sign 2\n");` (or similar) in your jetted functions. This will let us verify that the jets exist and are running.
756+ edit ~/tlon/urbit/jets/e/secp.c (or whatever) to include `fprintf(stderr, "*** u3we_sign 2\n");` (or similar) in your jetted functions. This will let us verify that the jets exist and are running.
757−+ `cd ~/tlon/urbit ; scripts/build `
757++ `cd ~/tlon/urbit ; sh/build `
758+ `cp ~/tlon/arvo ~/tlon/arvo_nojet`
758+ `cp ~/tlon/arvo ~/tlon/arvo_nojet`
759+ edit `~/tlon/arvo_nojet/sys/zuse_nojetting.hoon` to remove jetting
759+ edit `~/tlon/arvo_nojet/sys/zuse_nojetting.hoon` to remove jetting
760+ Because we can not run two instances of the same fake galaxy on the same machine (their ports would conflict), we need to pick a new galaxy name. Galaxy names are not arbitrary. You may not name your galaxy "mygalaxy", "withjet", "withoutjet", or anything like that. Galaxy names are restricted to the range 0-255, converted into pronounceable syllables. `zod` is just the pronunciation of '0' ( to see this, in a dojo, cast `~zod` to an untyped atom thusly: `` `@`~zod ``). Let's pick 1 as our new galaxy id. Use dojo to convert this into a urbit name: `` `@p`1 `` yields `~nec`.
760+ Because we can not run two instances of the same fake galaxy on the same machine (their ports would conflict), we need to pick a new galaxy name. Galaxy names are not arbitrary. You may not name your galaxy "mygalaxy", "withjet", "withoutjet", or anything like that. Galaxy names are restricted to the range 0-255, converted into pronounceable syllables. `zod` is just the pronunciation of '0' ( to see this, in a dojo, cast `~zod` to an untyped atom thusly: `` `@`~zod ``). Let's pick 1 as our new galaxy id. Use dojo to convert this into a urbit name: `` `@p`1 `` yields `~nec`.