ghc-tags-plugin 0.1.0.0 → 0.1.0.1
raw patch · 2 files changed
+35/−3 lines, 2 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- README.md +31/−0
- ghc-tags-plugin.cabal +4/−3
+ README.md view
@@ -0,0 +1,31 @@+# Ghc Tags Compiler Plugin+A [Ghc Compiler Plugin](https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/extending_ghc.html#compiler-plugins)+which generates tags for each compiled module or component. The source tree is+[left unmodified](https://github.com/coot/ghc-tags-plugin/blob/master/lib/Plugin/GhcTags.hs#L79).++# Usage+```+ghc -plugin-package=ghc-tags-plugin -fplugin=Plugin.GhcTags+```++If you're using `cabal`, at this point you will need to add `ghctags` to every+'build-depends' in every `*.cabal` file. That's unfortunate state of the+eco-system right now. You can add `ghc-options` to your `cabal.project.local`+file for each cabal project, e.g. (note that you'll need to update the+`CURRENT_GIT_TAG` below)++```+project someproject+ ghc-options: -fplugin=Plugin.GhcTags+++source-repository-package+ type: git+ location: /home/coot/repos/haskell/ghc-tags-plugin+ tag: CURRENT_GIT_TAG+ subdir: .++```++A `tags` file will be created (or destructively updated) in each project+directory (the same as its `cabal` file).
ghc-tags-plugin.cabal view
@@ -1,6 +1,6 @@ cabal-version: 2.4 name: ghc-tags-plugin-version: 0.1.0.0+version: 0.1.0.1 synopsis: A compiler plugin which generates tags file from GHC syntax tree. description: A compiler source plugin which takes parsed Haskell syntax tree and saves@@ -9,10 +9,11 @@ license-file: LICENSE author: Marcin Szamotulski maintainer: profunctor@pm.me-copyright: 2020, Marcin Szamotulski+copyright: (c) 2020, Marcin Szamotulski category: Development extra-source-files: CHANGELOG.md-homepage: https://github.com/coot#readme+ README.md+homepage: https://github.com/coot/ghc-tags-plugin#readme bug-reports: https://github.com/coot/ghc-tags-plugin/issues source-repository head