#7: add --ghc-args and such to configure ----------------------------------+----------------------------------------- Reporter: ijones | Owner: ijones Type: enhancement | Status: closed Priority: high | Milestone: Cabal-1.2 Component: Cabal | Version: 1.1.3 Severity: normal | Resolution: fixed Keywords: | Ghcversion: 6.2.1 Difficulty: very easy (<1 hour) | Platform: Linux ----------------------------------+----------------------------------------- Changes (by duncan): * resolution: => fixed * status: reopened => closed Comment: Now documented. Also, I've added a {{{--prog-arg=}}} flag that behaves like {{{--configure-option=}}}. I've also made {{{--prog-args=}}} parse it's args more cleverly. Instead of using words which breaks on files with embedded spaces we now use a slightly more clever lexer that allows simple quoting with "" chars. eg: {{{ splitArgs "--foo=\"C:\Program Files\Bar\" --baz" = ["--foo=C:\Program Files\Bar", "--baz"] }}} so on the command line you'd use: {{{ ./setup configure --foo-args='--bar="some path with spaces"' }}} That is the " chars have to be passed to setup, so if necessary they have to be escaped in the shell invocation. The alternative of course is to use {{{ ./setup configure --foo-arg=--bar="some path with spaces" }}} again, assuming your shell parses {{{--foo-arg=--bar="some path with spaces"}}} into a single argument {{{--foo-arg=--bar=some path with spaces}}}. Oh the joys of shell quoting. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/7 Hackage http://example.com/ My example project