Skip to content

Commit

Permalink
clarify top-level README
Browse files Browse the repository at this point in the history
We rarely need to clone the repository when writing a Swish application,
stand-alone or otherwise.
  • Loading branch information
owaddell-beckman committed May 6, 2024
1 parent 027e22f commit b288ea1
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,8 @@ and boot file, `osi.dll`, `uv.dll`, `sqlite3.dll`, Chez Scheme's
`csv964.dll` or the `csv*.dll` for the version you are using, and Microsoft's C Runtime Library
`vcruntime140.dll`.

Developers writing stand-alone applications should clone the Swish
repository and run `configure`. Swish's source repository provides
`swish.h` to define callable exports for `osi.dll`. `Mf-config` can be
used in makefiles to define variables for system-specific paths.
You can define most applications entirely in Scheme, using the Swish libraries.
If you need to integrate C code that relies on Swish exports, clone the Swish
repository and run `configure`. This generates a `src/swish/Mf-config` that your
makefile can `include` to define variables for system-specific paths.
Swish's source repository provides `swish.h` to define callable exports for `osi.dll`.

0 comments on commit b288ea1

Please sign in to comment.