summaryrefslogtreecommitdiff
path: root/libraries/ghc-boot/GHC/BaseDir.hs
Commit message (Collapse)AuthorAgeFilesLines
* Review suggestions for assorted fixes to avoid Data.List.{head,tail}sheaf2022-11-251-2/+3
|
* Assorted fixes to avoid Data.List.{head,tail}Bodigrim2022-11-251-2/+2
|
* Implement System.Environment.getExecutablePath for NetBSDPHO2022-02-091-2/+2
| | | | and also use it from GHC.BaseDir.getBaseDir
* Fix a few Note inconsistenciesBen Gamari2022-02-011-1/+1
|
* Use getExecutablePath in getBaseDir on OpenBSDGreg Steuck2021-11-251-2/+2
| | | | | | | | While OpenBSD doesn't have a general mechanism for determining the path of the executing program image, it is reasonable to rely on argv[0] which happens as a fallback in getExecutablePath. With this change on top of T18173 we can get a bit close to fixing #18173.
* Add explicit import lists to Data.List importsOleg Grenrus2021-01-291-1/+1
| | | | | | | | | | | | | Related to a future change in Data.List, https://downloads.haskell.org/ghc/8.10.3/docs/html/users_guide/using-warnings.html?highlight=wcompat#ghc-flag--Wcompat-unqualified-imports Companion pull&merge requests: - https://github.com/judah/haskeline/pull/153 - https://github.com/haskell/containers/pull/762 - https://gitlab.haskell.org/ghc/packages/hpc/-/merge_requests/9 After these the actual change in Data.List should be easy to do.
* Fix typos, using Wikipedia list of common typosBrian Wignall2019-11-281-1/+1
|
* ghc-pkg needs settings file to un-hardcode target platformJohn Ericson2019-06-191-1/+17
| | | | This matches GHC itself getting the target platform from there.
* Factor out 'getLibDir' / 'getBaseDir' into a new GHC.BaseDir ghc-boot moduleJohn Ericson2019-06-071-0/+61
ghc-pkg and ghc already both needed this. I figure it is better to deduplicate, especially seeing that changes to one (FreeBSD CPP) didn't make it to the other. Additionally in !1090 I make ghc-pkg look up the settings file, which makes it use the top dir a bit more widely. If that lands, any difference in the way they find the top dir would be more noticable. That change also means sharing more code between ghc and ghc-package (namely the settings file parsing code), so I'd think it better to get off the slipperly slope of duplicating code now.