[Hackage] #519: .cpphs files are processed using GHC's built-in CPP instead of cpphs
#519: .cpphs files are processed using GHC's built-in CPP instead of cpphs ----------------------------+----------------------------------------------- Reporter: Deewiant | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Currently, if you need to use `cpphs`, the only way of going about it is to define a custom `PreProcessor` in your `Setup.hs` and using it as an override in `hookedPreProcessors`. A seemingly sensible way of making this easier would be that `.cpphs` files prefer being processed by `cpphs` instead of GHC's built-in CPP. (Most people probably just use `{-# LANGUAGE CPP #-}` in a `.hs` for the latter anyway.) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/519 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#519: .cpphs files are processed using GHC's built-in CPP instead of cpphs ----------------------------+----------------------------------------------- Reporter: Deewiant | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: normal | Resolution: Keywords: | Difficulty: very easy (<1 hour) Ghcversion: | Platform: ----------------------------+----------------------------------------------- Changes (by duncan): * difficulty: unknown => very easy (<1 hour) Comment: Should be easy to switch it. Whoever does this should also test what the failure mode is when cpphs is not available and the package forgets to mention `build-tools: cpphs`. On a related note we should warn about any tools used that are not declared. Indeed perhaps we should say that packages that declare a minimum version of Cabal are actually opting in to stricter behaviour, like not configuring build tools that are not explicitly declared. Or perhaps that should be done by a different mechanism. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/519#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
participants (1)
-
Hackage