The issue uses consistency with -odir and -hieDir as a
rationalization. I think it's not quite right because inputs can have
a search path while outputs don't, but if it is true that -odir
simultaneously sets the output and input dir for `*.o`, that seems
confusing too. Shouldn't -odir set
The behavior of `-hidir` and `-i` changed in response to this issue:
https://gitlab.haskell.org/ghc/ghc/-/issues/16500
We just ran into this and I think the change is unfortunate. I don't think
`-hidir` (a flag about output) should override the input search flag. I
would like it to at least
Could be! I’m far from a computer much of this week
On Sat, Oct 23, 2021 at 2:36 PM Brandon Allbery wrote:
> I would expect that to be -I and for -i to specify module paths (which
> might well mean .hi).
>
> On Sat, Oct 23, 2021 at 2:32 PM Carter Schonwald <
> carter.schonw...@gmail.com>
I would expect that to be -I and for -i to specify module paths (which
might well mean .hi).
On Sat, Oct 23, 2021 at 2:32 PM Carter Schonwald
wrote:
> I would assume the -i is for include c header search paths but I could be
> wrong
>
> On Sat, Oct 23, 2021 at 6:00 AM Oleg Grenrus wrote:
>
>>
I would assume the -i is for include c header search paths but I could be
wrong
On Sat, Oct 23, 2021 at 6:00 AM Oleg Grenrus wrote:
> This looks like a bug.
>
> -hidir documentation says
>
> > Redirects all generated interface files into ⟨dir⟩, instead of the
> default.
> > Please also note
This looks like a bug.
-hidir documentation says
> Redirects all generated interface files into ⟨dir⟩, instead of the
default.
> Please also note that when doing incremental compilation (by ghc
--make or ghc -c), this directory is where GHC looks into to find
interface files.
And documentation
