On Thu, Jul 3, 2014 at 12:47 PM, Vlatko Basic wrote:

Hello Cafe,

I have a local forked package and added its path to sandboxed project with 'cabal sandbox add-source PATH'.

However, to build that package I have to specify a flag to 'cabal install'. In other words I can't install it by 'cabal install --only-dependencies', but separately with 'cabal install PACKAGE -fFLAG'.

Is there a way to tell cabal sandbox (or in project.cabal) to always use some flag(s) for compiling a (particular) package in local path?

A way of side stepping this problem is to setup a sandbox in the forked project directory with "cabal sandbox init --sandbox=../MyProject/.cabal-sandbox", then you can run "cabal install --flags" in the forked project directory, and it will install to the sandbox for your downstream project. Anthony

On Thu, Jul 3, 2014 at 9:47 AM, Vlatko Basic wrote:

Hello Cafe,

I have a local forked package and added its path to sandboxed project with 'cabal sandbox add-source PATH'.

However, to build that package I have to specify a flag to 'cabal install'. In other words I can't install it by 'cabal install --only-dependencies', but separately with 'cabal install PACKAGE -fFLAG'.

I believe you can use constraints to resolve this. eg: $ cabal install --only-dep --constraint="snap-server +openssl" to install snap-server (a dependency) with the openssl flag set. (Credit to Adam Foltzer for pointing this out to me yesterday, coincidentally.) --Rogan

Is there a way to tell cabal sandbox (or in project.cabal) to always use some flag(s) for compiling a (particular) package in local path?

GHC 7.8.2, Cabal 1.20.0

Best regards,

vlatko _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

You could try adding that constraint with the flag to the cabal.config in the sandbox. Something like: Constraint: snap-server +openssl I've put constraints there before, but I'm not sure if the flag syntax works in that spot. Erik On Fri, Jul 4, 2014 at 3:07 PM, Vlatko Basic wrote:

Hi Rogan,

Thanks for the tip. It works as you said. Good to know.

However, this the same as manually installing the package with 'cabal install'. I'm trying to find a solution to bind the flag with the source permanently, so when you specify it once, no need to mention it again.

vlatko

-------- Original Message -------- Subject: Re: [Haskell-cafe] Specifying cabal sandbox flag for local package From: Rogan Creswick To: vlatko.basic@gmail.com Cc: haskell-cafe Date: 03.07.2014 22:09

On Thu, Jul 3, 2014 at 9:47 AM, Vlatko Basic wrote:

...

Hello Cafe,

I have a local forked package and added its path to sandboxed project with 'cabal sandbox add-source PATH'.

However, to build that package I have to specify a flag to 'cabal install'. In other words I can't install it by 'cabal install --only-dependencies', but separately with 'cabal install PACKAGE -fFLAG'.

I believe you can use constraints to resolve this.

eg:

$ cabal install --only-dep --constraint="snap-server +openssl"

to install snap-server (a dependency) with the openssl flag set.

(Credit to Adam Foltzer for pointing this out to me yesterday, coincidentally.)

--Rogan

...

Is there a way to tell cabal sandbox (or in project.cabal) to always use some flag(s) for compiling a (particular) package in local path?

GHC 7.8.2, Cabal 1.20.0

Best regards,

vlatko _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe