Skip to content

.cpphs files are processed using GHC's built-in CPP instead of cpphs #512

Closed
bos opened this Issue May 24, 2012 · 2 comments

2 participants

@bos
Haskell member
bos commented May 24, 2012

(Imported from Trac #519, reported by Deewiant on 2009-03-07)

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.)

@bos
Haskell member
bos commented May 24, 2012

(Imported comment by @dcoutts on 2009-03-07)

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.

@tibbe
Haskell member
tibbe commented May 15, 2014

Closing as there's been no activity in years.

We're cleaning up the bug tracker to make it useful again and are thus closing bugs that haven't seen any activity in a long time. Please re-open (or file a new bug) if the problem reappears.

@tibbe tibbe closed this May 15, 2014
@tibbe tibbe reopened this May 15, 2014
@tibbe tibbe closed this May 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.