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

revised info on DESTDIR, because I didn't quite understand the old text; hopefully the new text still makes sense to others

Browse Source 
svn: r3474
This commit is contained in:
Matthew Flatt 2006-06-26 01:33:53 +00:00
parent d540970a9a
commit 1512697f12
1 changed files with 11 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
src/README
View File

@ -150,19 +150,18 @@ the Unix instructions below, but note the following:
executable directory for a --prefix build. executable directory for a --prefix build.
For a --prefix build, this step also creates a "config.ss" module For a --prefix build, this step also creates a "config.ss" module
in a "config" collection for a --prefix build, so that various PLT in a "config" collection, so that various PLT tools and libraries
tools and libraries can find the installation directories. In can find the installation directories. At this stage, in case you
this case, you can also use a `DESTDIR' environment variable to are packaging an installation instead of installing directly, you
have the hierarchy constructed at a temporary place (useful for can redirect the installation by setting the "DESTDIR" environment
packaging), for example: `make DESTDIR=/tmp/plt-build install'. variable. For example, `make DESTDIR=/tmp/plt-build install'
Note that if DESTDIR is used, the resulting installation will not places the installation into "/tmp/plt-build" instead of the
be functional until it is installed in the its intended place location originally specified with --prefix. The resulting
(because at the end of this step, the generated "config.ss", the installation will not work, however, until it is moved to the
binaries and the launchers will all get patched to point at the location originally specified with --prefix.
installation paths, without the DESTDIR prefix).
Finally, this step compiles ".zo" bytecode files for installed Finally, the `make install' step compiles ".zo" bytecode files for
Scheme source, and generates launcher programs like installed Scheme source, and generates launcher programs like
"DrScheme". Use `make plain-install' to install without compiling "DrScheme". Use `make plain-install' to install without compiling
".zo" files or creating launchers. ".zo" files or creating launchers.