Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
Glasgow Haskell Compiler
GHC
Commits
1b964925
Commit
1b964925
authored
Aug 24, 1999
by
simonpj
Browse files
[project @ 1999-08-24 09:31:07 by simonpj]
Document the -i effect on recompilation
parent
7d845299
Changes
1
Hide whitespace changes
Inline
Side-by-side
ghc/docs/users_guide/using.vsgml
View file @
1b964925
...
...
@@ -508,6 +508,8 @@ it looks.
<tag>@-i<dirs>@</tag><nidx>-i<dirs> option</nidx> This flag
prepends a colon-separated list of @dirs@ to the ``import
directories'' list.
See also Section <ref id="recomp"> for the significance of using
relative and absolute pathnames in the @-i@ list.
<tag>@-i@</tag> resets the ``import directories'' list back to nothing.
...
...
@@ -614,18 +616,24 @@ signature within the interface file. It also keeps in every interface
file a list of the version numbers of everything it used when it last
compiled the file. If the source file's modification date is earlier
than the @.o@ file's date (i.e. the source hasn't changed since the
file was last compiled), and you give GHC the @-recomp@<nidx>-recomp
option</nidx> flag, then GHC will be clever. It compares the version
file was last compiled), GHC will be clever. It compares the version
numbers on the things it needs this time with the version numbers on
the things it needed last time (gleaned from the interface file of the
module being compiled); if they are all the same it stops compiling
rather early in the process saying ``Compilation IS NOT required''.
What a beautiful sight!
It's still an experimental feature (that's why @-recomp@ is off by
default), so tell us if you think it doesn't work.
Patrick Sansom has a workshop paper about how all this is done. Ask
GHC <em>only</em> keeps detailed dependency information for ``user'' modules,
not for ``library'' modules. It distinguishes the two by a hack: a module
whose @.hi@ file has an absolute path name is considered a library module,
while a relative path name indicates a user module. So if you have a
multi-directory application, use <em>relative</em> path names in your
@-i@ path, to force GHC to record detailed dependency information.
Use absolute path names only for directories containing slowly-changing
library modules.
Patrick Sansom had a workshop paper about how all this is done (though
the details have changed quite a bit). Ask
him (email: <htmlurl name="sansom@@dcs.gla.ac.uk"
url="mailto:sansom@@dcs.gla.ac.uk">) if you want a copy.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment