Distribution.Simple.PreProcess

This defines a PreProcessor abstraction which represents a pre-processor that can transform one kind of file into another. There is also a PPSuffixHandler which is a combination of a file extension and a function for configuring a PreProcessor. It defines a bunch of known built-in preprocessors like cpp, cpphs, c2hs, hsc2hs, happy, alex etc and lists them in knownSuffixHandlers. On top of this it provides a function for actually preprocessing some sources given a bunch of known suffix handlers. This module is not as good as it could be, it could really do with a rewrite to address some of the problems we have with pre-processors.

Documentation

preprocessComponent :: PackageDescription -> Component -> LocalBuildInfo -> Bool -> Verbosity -> [PPSuffixHandler] -> IO ()

Apply preprocessors to the sources from hsSourceDirs for a given component (lib, exe, or test suite).

knownSuffixHandlers :: [PPSuffixHandler]

Standard preprocessors: GreenCard, c2hs, hsc2hs, happy, alex and cpphs.

ppSuffixes :: [PPSuffixHandler] -> [String]

Convenience function; get the suffixes of these preprocessors.

type PPSuffixHandler = (String, BuildInfo -> LocalBuildInfo -> PreProcessor)

A preprocessor for turning non-Haskell files with the given extension into plain Haskell source files.

data PreProcessor

The interface to a preprocessor, which may be implemented using an external program, but need not be. The arguments are the name of the input file, the name of the output file and a verbosity level. Here is a simple example that merely prepends a comment to the given source file:

 ppTestHandler :: PreProcessor
 ppTestHandler =
   PreProcessor {
     platformIndependent = True,
     runPreProcessor = mkSimplePreProcessor $ \inFile outFile verbosity ->
       do info verbosity (inFile++" has been preprocessed to "++outFile)
          stuff <- readFile inFile
          writeFile outFile ("-- preprocessed as a test\n\n" ++ stuff)
          return ExitSuccess

We split the input and output file names into a base directory and the rest of the file name. The input base dir is the path in the list of search dirs that this file was found in. The output base dir is the build dir where all the generated source files are put.

The reason for splitting it up this way is that some pre-processors don't simply generate one output .hs file from one input file but have dependencies on other genereated files (notably c2hs, where building one .hs file may require reading other .chi files, and then compiling the .hs file may require reading a generated .h file). In these cases the generated files need to embed relative path names to each other (eg the generated .hs file mentions the .h file in the FFI imports). This path must be relative to the base directory where the genereated files are located, it cannot be relative to the top level of the build tree because the compilers do not look for .h files relative to there, ie we do not use "-I .", instead we use "-I dist/build" (or whatever dist dir has been set by the user)

Most pre-processors do not care of course, so mkSimplePreProcessor and runSimplePreProcessor functions handle the simple case.

Constructors

PreProcessor

Fields

platformIndependent :: Bool

runPreProcessor :: (FilePath, FilePath) -> (FilePath, FilePath) -> Verbosity -> IO ()

mkSimplePreProcessor :: (FilePath -> FilePath -> Verbosity -> IO ()) -> (FilePath, FilePath) -> (FilePath, FilePath) -> Verbosity -> IO ()

runSimplePreProcessor :: PreProcessor -> FilePath -> FilePath -> Verbosity -> IO ()

ppCpp :: BuildInfo -> LocalBuildInfo -> PreProcessor

ppCpp' :: [String] -> BuildInfo -> LocalBuildInfo -> PreProcessor

ppGreenCard :: BuildInfo -> LocalBuildInfo -> PreProcessor

ppC2hs :: BuildInfo -> LocalBuildInfo -> PreProcessor

ppHsc2hs :: BuildInfo -> LocalBuildInfo -> PreProcessor

ppHappy :: BuildInfo -> LocalBuildInfo -> PreProcessor

ppAlex :: BuildInfo -> LocalBuildInfo -> PreProcessor

ppUnlit :: PreProcessor

platformDefines :: LocalBuildInfo -> [String]