suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix typos on windows build README (#2919)

Browse Source
This commit is contained in:
Paulo Matos 2019-11-23 22:00:21 +01:00 committed by GitHub
parent d1bfa6a203
commit aecee7ff30
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
racket/src/worksp/README.txt
View File

@ -58,7 +58,7 @@ The result is "..\..\Racket.exe", DLLs and "GRacket.exe" in
Many intermediate files will be put in "../build", including a Chez
Scheme checkout if it's not already present there; if a "ChezScheme"
directory exists in the Racket suorce directory, it is copied to the
directory exists in the Racket source directory, it is copied to the
build directory, otherwise it is cloned from a Git repository (in
which case `git` must be available).
@ -69,11 +69,11 @@ Both Traditional Racket and Racket-on-Chez
When using "csbuild.rkt" directly, omit the `--racketcs-suffix ""`
arguments to create "..\..\RacketCS.exe" executable instead of
"..\..\RacketCS.exe". A build with a "CS" suffix is also configured to
"..\..\Racket.exe". A build with a "CS" suffix is also configured to
read and bytecode in a subdirectory of "compiled" as described in
"..\cs\README.txt".
A "CS" and using a subdirectoryu of "compiled" means that a
A "CS" suffix and using a subdirectory of "compiled" means that a
Racket-on-Chez build as "RacketCS.exe" can coexist with a
traditional build as "Racket.exe". So, the sequence