Meta tags:
description=A program for developing Haskell projects. ;
author=Stack contributors;

Headings (most frequently used words):

packages, developing, on, windows, updating, the, stack, supplied, msys2, setup, hs, pacman, to, install, for, common, haskell,

Text of the page (most frequently used words):
stack (44), the (39), msys2 (20), pacman (18), environment (16), and (13), for (12), windows (12), with (10), exec (10), #packages (10), clang64 (9), path (8), supplied (8), can (7), project (7), configuration (7), files (7), build (6), haskell (6), you (6), command (6), setup (6), directories (6), package (6), help (6), config (5), install (5), see (5), version (5), relevant (5), other (5), bin (5), commands (5), developing (5), ghc (5), pkg (4), common (4), run (4), need (4), more (4), updating (4), about (4), specific (4), includes (4), include (4), started (4), configure (4), contributors (3), cabal (3), installation (3), some (3), this (3), than (3), guide (3), non (3), extra (3), libraries (3), your (3), example (3), those (3), all (3), tools (3), obtained (3), operation (3), get (3), involved (3), integration (3), building (3), topics (3), getting (3), flag (2), zlib (2), pkgconf (2), default (2), executable (2), icu (2), additional (2), file (2), may (2), update (2), library (2), corresponding (2), dirs (2), will (2), usr (2), installed (2), like (2), using (2), sync (2), which (2), terminal (2), use (2), executing (2), used (2), shell (2), scripts (2), table (2), contents (2), glossary (2), faq (2), how (2), works (2), upgrading (2), maintainers (2), code (2), docker (2), script (2), snapshot (2), location (2), flags (2), options (2), projects (2), setting (2), welcome (2), github (2), made, material, mkdocs, copyright, 2015, 2025, back, top, alternatively, requires, its, implementation, defaults, true, mingw, w64, clang, x86_64, text, following, lists, known, allow, feel, free, submit, entries, via, pull, request, automatically, inside, when, launch, another, tool, not, prefix, within, custom, once, until, everything, reported, date, nothing, suy, itself, updated, has, that, 6403, greater, then, simply, further, information, configuring, option, documentation, msys, searched, header, system, lib, directory, depends, dynamic, link, want, outside, ensure, copies, are, local, executables, manager, found, management, also, available, should, operations, equivalently, index, matter, software, choose, console, host, prompt, powershell, git, bash, any, too, programs, through, program_name, comes, bit, provide, unix, necessary, installing, such, needs, during, phase, history, resources, overview, signing, key, self, hosted, runners, haskellstack, org, zip, add, maintainer, team, process, releases, scheme, dev, containers, contributor, lock, azure, travis, auto, completion, visual, studio, editor, debugging, from, source, standard, initialization, nix, interpreter, yaml, specification, work, root, customisation, global, directive, variables, upload, upgrade, unpack, uninstall, test, templates, sdist, runhaskell, runghc, repl, query, purge, new, list, init, ide, hpc, hoogle, haddock, ghci, eval, dot, clean, bench, conclusion, interactively, locations, multi, targets, synonyms, databases, existing, description, hello, world, initializing, search, skip, content,

Text of the page (random words):
developing on windows stack skip to content stack developing on windows initializing search github welcome setting up getting started commands configure topics get involved faq glossary more stack github welcome setting up getting started getting started 1 a hello world example 2 package description 3 project configuration 4 building your project 5 building existing projects 6 installed package databases 7 stack build synonyms 8 stack build targets 9 multi package projects 10 cabal flags and ghc options 11 locations used by stack 12 executing commands 13 using ghc interactively 14 stack configuration 15 in conclusion commands commands bench build clean config dot docker eval exec ghc ghci haddock hoogle hpc ide init install list ls new path purge query repl run runghc runhaskell script sdist setup templates test uninstall unpack update upgrade upload configure configure environment variables configuration files configuration files project specific configuration non project specific configuration the include directive global flags and options customisation scripts topics topics stack root stack work directories stack environment snapshot location package location snapshot specification stack yaml vs a cabal file script interpreter docker integration nix integration non standard project initialization building ghc from source debugging editor integration stack and visual studio code developing on windows developing on windows table of contents updating the stack supplied msys2 setup hs pacman packages to install for common haskell packages shell auto completion ci travis ci azure ci lock files haskell and c code get involved get involved contributors contributors contributor s guide dev containers maintainers maintainers version scheme releases maintainer team process add ghc version upgrading msys2 upgrading 7 zip haskellstack org self hosted runners signing key how stack works how stack works build overview faq glossary more more other resources version history table of contents updating the stack supplied msys2 setup hs pacman packages to install for common haskell packages developing on windows on windows stack comes with an installation of msys2 an environment of msys2 by default clang64 on 64 bit windows will be used by stack to provide a unix like shell and environment for stack this may be necessary for installing some haskell packages such as those which use configure scripts or if your project needs some additional tools during the build phase no matter which terminal software you choose windows terminal console windows host command prompt powershell git bash or any other you can use this environment too by executing all programs through stack exec program_name executables and libraries can be installed with the msys2 package manager pacman all tools can be found in the index to msys2 packages a guide to package management with pacman is also available pacman like all other tools in the stack environment should be started with stack exec pacman help about pacman commands operations can be obtained by stack exec pacman help help about a specific pacman operation can be obtained by using help or h with an operation for example help about the operation sync or s can be obtained with stack exec pacman sync help or equivalently stack exec pacman sh command stack path bin path to see the path in the stack environment if the relevant msys2 environment is clang64 on windows it includes the clang64 bin usr local bin and usr bin directories of the stack supplied msys2 it includes the corresponding directory if the relevant msys2 environment is other than clang64 if your executable depends on files for example dynamic link libraries in those directories and you want to run it outside of the stack environment you will need to ensure copies of those files are on the path command stack path extra include dirs and stack path extra library dirs to see the extra directories searched for c header files or system libraries files in the stack environment if the relevant msys2 environment is clang64 on windows it includes the clang64 include include and the clang64 lib and clang64 bin directories library of the stack supplied msys2 it includes the corresponding directories if the relevant msys2 environment is other than clang64 for further information about configuring the relevant msys2 environment see stack s msys environment non project specific configuration option documentation updating the stack supplied msys2 the stack supplied msys2 can itself be updated with the stack supplied pacman see the msys2 guide updating msys2 if the stack supplied pacman has a version that is 5 0 1 6403 or greater see stack exec pacman version then the command to update is simply stack exec pacman suy this command may need to be run more than once until everything is reported by pacman as up to date and nothing to do setup hs setup hs is automatically run inside the stack environment so when you need to launch another tool you do not need to prefix the command with stack exec within the custom setup hs file pacman packages to install for common haskell packages the following lists msys2 packages known to allow the installation of some common haskell packages on windows feel free to submit additional entries via a pull request for text icu install mingw w64 clang x86_64 icu for zlib 0 7 the default cabal flag pkg config is true and requires executable pkg config on the path msys2 defaults to pkgconf as its pkg config implementation installation stack exec pacman s pkgconf alternatively build with flag zlib pkg config back to top copyright c 2015 2025 stack contributors made with material for mkdocs