
I notice that some of GHC's command-line parameters do not work from within the OPTIONS_GHC pragma (6.6.1 on Windows). I can see how that makes sense for some parameters like "--make", but what about "-i" and "-v"? Is this intentional or a bug? Can't specify the include path: {-# OPTIONS_GHC -iMyDir #-} Can't compile a single file in 'verbose' mode: {-# OPTIONS_GHC -v #-} Thanks, Greg

On Tue, Jul 24, 2007 at 01:21:00PM -0700, Greg Fitzgerald wrote:
I notice that some of GHC's command-line parameters do not work from within the OPTIONS_GHC pragma (6.6.1 on Windows). I can see how that makes sense for some parameters like "--make", but what about "-i" and "-v"? Is this intentional or a bug?
Can't specify the include path: {-# OPTIONS_GHC -iMyDir #-}
Can't compile a single file in 'verbose' mode: {-# OPTIONS_GHC -v #-}
Thanks, Greg
It's quite intentional, and documented. http://haskell.org/ghc/dist/current/docs/users_guide/static-dynamic-flags.ht... (that said, more parameters are static than really should be, esp in older versions of GHC) Stefan
participants (2)
-
Greg Fitzgerald
-
Stefan O'Rear