Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
gershomb
GHC
Commits
e5f13b3a
Unverified
Commit
e5f13b3a
authored
6 years ago
by
Andrey Mokhov
Committed by
GitHub
6 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Tweak the build root section
parent
798a716b
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+5
-6
5 additions, 6 deletions
README.md
with
5 additions
and
6 deletions
README.md
+
5
−
6
View file @
e5f13b3a
...
...
@@ -59,12 +59,11 @@ In addition to standard Shake flags (try `--help`), the build system
currently supports several others:
*
`--build-root=PATH`
or
`-oPATH`
: specify the directory in which you want to store all
the build artifacts. If none is specified by the user, hadrian will store everything
under
`_build/`
at the top of ghc's source tree. Unlike GHC's make build system,
hadrian doesn't have any "inplace" logic left anymore. This option is therefore
useful for GHC developers who want to build GHC in different ways or at different
commits, from the same directory, and have the build products sit in different,
isolated folders.
build products. By default Hadrian builds everything in the
`_build/`
subdirectory of
the GHC source tree. Unlike the Make build system, Hadrian doesn't have any "inplace"
logic left anymore. This option is therefore useful for GHC developers who want to build
GHC in different ways or at different commits, from the same source directory, and have
the build products sit in different, isolated folders.
*
`--configure`
or
`-c`
: use this flag to run the
`boot`
and
`configure`
scripts
automatically, so that you don't have to remember to run them manually as you normally
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment