for this. You'd need to include your
preprocessor source in the extra-source-files field of build-depends. In
this case cabal won't know anything about the preprocessor, ghc will run it
directly.
On Dec 6, 2013 7:31 PM, Peter Selinger selin...@mathstat.dal.ca wrote:
This may be a silly question, but I
That is a good point. I'll try it. -- Peter
Dag Odenhall wrote:
How about -pgmF runghc -optF PreProc?
On Mon, Dec 9, 2013 at 12:48 AM, Peter Selinger
selin...@mathstat.dal.cawrote:
Thanks for the suggestion! However, it is not portable: it doesn't
work on Windows.
Similarly
use runghc to run a proprocessor.
Thanks, -- Peter
Dag Odenhall wrote:
How about -pgmF runghc -optF PreProc?
On Mon, Dec 9, 2013 at 12:48 AM, Peter Selinger
selin...@mathstat.dal.cawrote:
Thanks for the suggestion! However, it is not portable: it doesn't
work on Windows
I agree. Two of my packages are in your list: easyrender and newsynth
(both have Nothing for a reason in your list).
The problem for me is that, although you seem to have access to build
logs, I don't. I have not found the way to access the hackage build
logs for my packages or their
could not be solved, there is no way of
knowing really.
Thanks again, -- Peter
Mateusz Kowalczyk wrote:
On 05/01/14 18:15, Peter Selinger wrote:
I agree. Two of my packages are in your list: easyrender and newsynth
(both have Nothing for a reason in your list).
If a package has Nothing
Thanks, that's even better!
However, I find that the --contents-location option to cabal haddock
does not work properly. Apparently it not only prevents index.html
from being built (which makes modest sense), but it also prevents
index-frames.html from being built (which does not). So in the
Hi Mateusz,
of course you could do the same thing with a bash script. It's a
matter of personal taste and workflow. Just for the record, you can
pass arguments into a Makefile like this: make PACKAGE=bla. And $$
is indeed an escape, to denote a literal dollar sign (as opposed to a
Makefile
