Correct typos: INSTALL.txt, MzCOM, ffi/com
This commit is contained in:
parent
018e950634
commit
7a2be548c8
10
INSTALL.txt
10
INSTALL.txt
|
@ -28,7 +28,7 @@ win32-in-place', as long as you're using Microsoft Visual Studio 9.0
|
||||||
want more control over the process, see below.
|
want more control over the process, see below.
|
||||||
|
|
||||||
On Mac OS X and Windows, you'll need native-library packages in the
|
On Mac OS X and Windows, you'll need native-library packages in the
|
||||||
"native-pkgs" directory. In the git repostory, "native-pkgs" is a git
|
"native-pkgs" directory. In the git repository, "native-pkgs" is a git
|
||||||
submodule, so you'll need
|
submodule, so you'll need
|
||||||
git submodule init
|
git submodule init
|
||||||
git submodule update
|
git submodule update
|
||||||
|
@ -148,7 +148,7 @@ The `pkg-links' makefile target installs links to a specific
|
||||||
include "devel-pkgs" in the search path for packages. As a result, the
|
include "devel-pkgs" in the search path for packages. As a result, the
|
||||||
package links are installation specific, but still isolated from any
|
package links are installation specific, but still isolated from any
|
||||||
`installation'-scope packages that you install later. The `pkg-links'
|
`installation'-scope packages that you install later. The `pkg-links'
|
||||||
target alsosets the default package scope for the build to
|
target also sets the default package scope for the build to
|
||||||
`installation' mode. Both of those configuration adjustments are made
|
`installation' mode. Both of those configuration adjustments are made
|
||||||
only if no configuration file "racket/etc/config.rktd" exists already.
|
only if no configuration file "racket/etc/config.rktd" exists already.
|
||||||
|
|
||||||
|
@ -329,7 +329,7 @@ Roughly, the steps are
|
||||||
nmake win32-client SERVER=... PKGS="..."
|
nmake win32-client SERVER=... PKGS="..."
|
||||||
|
|
||||||
Add `SERVER_PORT=...' to the `client' line if you picked an
|
Add `SERVER_PORT=...' to the `client' line if you picked an
|
||||||
alternate port in the `server` line; it shoul dbe the same as for
|
alternate port in the `server` line; it should be the same as for
|
||||||
the `server' line.
|
the `server' line.
|
||||||
|
|
||||||
Add `DOC_SEARCH="..."' to the `client' line, if needed;
|
Add `DOC_SEARCH="..."' to the `client' line, if needed;
|
||||||
|
@ -380,7 +380,7 @@ In more detail:
|
||||||
`server-from-base' (i.e., steps 1a and 1b).
|
`server-from-base' (i.e., steps 1a and 1b).
|
||||||
|
|
||||||
The `SERVER_PORT' and `SERVER_HOSTS' variables of the makefile
|
The `SERVER_PORT' and `SERVER_HOSTS' variables of the makefile
|
||||||
configure the prt and interfaces of the server.
|
configure the port and interfaces of the server.
|
||||||
|
|
||||||
The `PKGS' variable of the makefile determines which packages are
|
The `PKGS' variable of the makefile determines which packages are
|
||||||
built for potential inclusion in a distribution.
|
built for potential inclusion in a distribution.
|
||||||
|
@ -415,7 +415,7 @@ In more detail:
|
||||||
that.
|
that.
|
||||||
|
|
||||||
Provide `SERVER' as the hostname of the server machine, but a
|
Provide `SERVER' as the hostname of the server machine, but a
|
||||||
"locahost"-based tunnel back to the server is more secure and
|
"localhost"-based tunnel back to the server is more secure and
|
||||||
avoids the need to specify `SERVER_HOSTS' when starting the
|
avoids the need to specify `SERVER_HOSTS' when starting the
|
||||||
server in step 1b. Also, provide `SERVER_PORT' if an alternate
|
server in step 1b. Also, provide `SERVER_PORT' if an alternate
|
||||||
port was specified in step 1b.
|
port was specified in step 1b.
|
||||||
|
|
|
@ -22,7 +22,7 @@ folder, re-register @exec{MzCOM.exe} with
|
||||||
|
|
||||||
@commandline{mzcom.exe /RegServer}
|
@commandline{mzcom.exe /RegServer}
|
||||||
|
|
||||||
The @exec{MzCOM.exe} executable find DLLs and Racket library
|
The @exec{MzCOM.exe} executable will find DLLs and Racket library
|
||||||
collections relative to its own path.
|
collections relative to its own path.
|
||||||
|
|
||||||
@; ----------------------------------------------------------------------
|
@; ----------------------------------------------------------------------
|
||||||
|
@ -163,7 +163,7 @@ loaded. If an expression kills the primary Racket thread, as in
|
||||||
]
|
]
|
||||||
|
|
||||||
then the evaluator Win32 thread is also killed.
|
then the evaluator Win32 thread is also killed.
|
||||||
When that happens, subsequent calls to Eval() will fail.
|
When that happens, subsequent calls to @tt{Eval} will fail.
|
||||||
|
|
||||||
@section{Acknowledgments}
|
@section{Acknowledgments}
|
||||||
|
|
||||||
|
|
|
@ -363,7 +363,7 @@ Removes any existing callback for @racket[name] in @racket[obj].}
|
||||||
|
|
||||||
Extracts an @cpp{IUnknown} or @cpp{IDispatch} pointer from
|
Extracts an @cpp{IUnknown} or @cpp{IDispatch} pointer from
|
||||||
@racket[obj]. The former succeeds for any @tech{COM object} that has
|
@racket[obj]. The former succeeds for any @tech{COM object} that has
|
||||||
not been relased via @racket[com-release]. The latter succeeds
|
not been released via @racket[com-release]. The latter succeeds
|
||||||
only when the @tech{COM object} supports @cpp{IDispatch}, otherwise
|
only when the @tech{COM object} supports @cpp{IDispatch}, otherwise
|
||||||
@racket[exn:fail] is raised.}
|
@racket[exn:fail] is raised.}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user