You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BUILDING.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,20 @@
1
1
# How to Build Medley and make a Release
2
2
3
+
The files in the Medley repository are used for making "loadups" lisp.sysout, full.sysout, apps.sysout. In order to build the Medley images, you need to have a build of "Maiko" (in flavors 'ldeinit' and 'lde' and either (`ldex` or `ldesdl`). Head over to the `Interlisp/maiko` repository to find out about making those.
4
+
3
5
# Using GitHub actions
4
6
7
+
Note that GitHub actions are used to automate the build process and insure that the system is built using known files, and that the releases are coordinated across platforms. We try to minimize dependencies on GitHub.
8
+
9
+
That said, you can manually trigger the automatic making of Medley loadups.
10
+
5
11
In the GitHub medley repository (Interlisp/medley) go to the Actions tab.
6
12
7
13
It will list the available GitHub actions.
8
14
Select: **Build/Push Release & Docker**.
9
15
10
16
In the middle of the screen there is a box labeled "Workflow Runs".
17
+
11
18
There should be a row in it that states 'This workflow has a workflow_dispatch event trigger' with a drop down menu (it really looks more like a button) on the right side labeled 'Run workflow'. Select that and you'll get a form allowing you to select the branch (I've only used Master) and enter the release name. Enter a name or leave it empty and press the green 'Run workflow' button. The workflow should queue up and run.
12
19
13
20
Build/Push Release & Docker first builds Maiko and Medley, pushes a Medley release to the Interlisp/medley repo Releases, then makes a Docker image.
@@ -59,6 +66,15 @@ The script "loadup-all.sh" itself involes scripts used for different steps in th
59
66
*`loadup-db.sh`
60
67
*`copy-all.sh`
61
68
69
+
Most of these scripts should only be run from the 'medley' repository top level directory.
70
+
71
+
```
72
+
your-working-area
73
+
maiko
74
+
medley
75
+
notecards
76
+
```
77
+
62
78
These are explained in reverse order:
63
79
64
80
### `copy-all.sh`: copy files from build directory to loadups
@@ -85,7 +101,7 @@ Masterscope has some gaps and bugs so `fuller.database` isn't as useful as it co
`apps.sysout` includes some other components that are part of online.interlisp.org experience.
104
+
`apps.sysout` includes some other components that are part of online.interlisp.org experience. In particular, you need `notecards`, which is in a separate repository (currently).
89
105
90
106
### `loadup-full-from-lisp.sh`: Build a `full.sysout` and
0 commit comments