Hackage :: [Package]

stack-wrapper: Call ghc within stack by calling ghc

[ bsd3, development, library, program ] [ Propose Tags ] [ Report a vulnerability ]

When you invoke ghc of stack-wrapper, you can invoke the appropriate one which specified by the resolver of stack.yaml.

[Skip to Readme]

Modules

  • StackWrapper

Downloads

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.1.0
Change log ChangeLog.md
Dependencies base (>=4.7 && <4.8), filepath (>=1.4), process (>=1.2), stack-wrapper [details]
License BSD-3-Clause
Copyright Kazuki Okamoto
Author Kazuki Okamoto
Maintainer kazuki.okamoto@kakkun61.com
Revised Revision 1 made by kakkun61 at 2019-12-02T11:00:30Z
Category Development
Home page https://github.com/kakkun61/stack-wrapper#readme
Bug tracker https://github.com/kakkun61/stack-wrapper/issues
Source repo head: git clone https://github.com/kakkun61/stack-wrapper
Uploaded by kakkun61 at 2019-12-02T05:31:17Z
Distributions
Executables runhaskell, runghc, hsc2hs, hp2ps, haddock, ghci, ghc-pkg, ghc, exe
Downloads 456 total (1 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
All reported builds failed as of 2019-12-02 [all 3 reports]

Readme for stack-wrapper-0.1.0

[back to package description]

stack-wrapper

When you invoke ghc of stack-wrapper, you can invoke the appropriate one which specified by the resolver of stack.yaml.

This helps you when you are working with stack but developing tools etc. don't support stack.

To check a stack-wrapper version, you give --stack-wrapper as the first option to commands.

You can set the default executable files with environment variables. They are used when no executable files found except the stack-wrapper's ones.

This package creates 2 types of executable files.

ghc etc.

ghc runs like:

  1. search a compiler under stack environment
  2. give the global, snapshot and local package DB to the compiler
  3. run the compiler

ghc-pkg, ghci, haddock, hp2ps, hsc2hs, runghc and runhaskell are also given.

exe

An executable file which is renamed from exe, for example hhpc, runs new process stack exec -- hhpc.

Options

  • --stack-wrapper
    • print the stack-wrapper version

Environment variables

  • STACK_WRAPPER_GHC_DIR
    • the default directory which contains ghc, ghc-pkg etc.
  • STACK_WRAPPER_<exe name>
    • the default executable file for <exe name>
    • on Windows remove the .exe extension