Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
Cabal
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
Julian Ospald
Cabal
Commits
9b9c1a7d
Commit
9b9c1a7d
authored
7 years ago
by
Erik de Castro Lopo
Browse files
Options
Downloads
Patches
Plain Diff
cabal-install.cabal: Improve comments for monolithic flag
parent
967a64e3
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cabal-install/cabal-install.cabal
+9
-8
9 additions, 8 deletions
cabal-install/cabal-install.cabal
with
9 additions
and
8 deletions
cabal-install/cabal-install.cabal
+
9
−
8
View file @
9b9c1a7d
...
...
@@ -130,13 +130,14 @@ flag lib
Default: False
manual: True
-- When we do CI, we build our binaries on one machine, and then
-- ship them to another machine for testing. Because we use
-- static linking (since it makes this sort of redeploy MUCH
-- easier), if we build five executables, that means we
-- need to ship ALL the Haskell libraries five times. That's
-- a waste of space! A better strategy is to statically link
-- everything into a single binary. That's what this flag does.
-- Build everything (including the test binaries) as a single static binary
-- instead of 5 discrete binaries.
-- This is useful for CI where we build our binaries on one machine, and then
-- ship them to another machine for testing. Since the test binaries are
-- statically linked (making deployment easier), if we build five executables,
-- that means we need to ship ALL 5 binaries (with 5 versions of all the
-- statically linked libraries) to the test machines. This reduces that to one
-- binary and one set of linked libraries.
flag monolithic
description: Build cabal-install also with all of its test and support code. Used by our continuous integration.
default: False
...
...
@@ -488,7 +489,7 @@ executable cabal
if !(arch(arm) && impl(ghc < 7.6))
ghc-options: -threaded
-- On AIX, some legacy BSD operations such as flock(2) are provided by libbsd.a
if os(aix)
extra-libraries: bsd
...
...
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