#177: Include-dirs, extra-lib-dirs with spaces doesn't work under Windows ---------------------+------------------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: Windows ---------------------+------------------------------------------------------ Comment (by ross@soi.city.ac.uk): Yes, this is documented behaviour, and can't be changed because we need to preserve backwards compatibility for the .cabal file format. But I also think space separators are a good thing, both for human editing and machine-generated field values. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/177#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects

#177: Check Include-dirs, extra-lib-dirs etc exist at configure time. ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: easy (<4 hours) Ghcversion: 6.6 | Platform: Windows ----------------------------+----------------------------------------------- Changes (by duncan): * difficulty: normal => easy (<4 hours) * summary: Include-dirs, extra-lib-dirs with spaces doesn't work under Windows => Check Include-dirs, extra-lib-dirs etc exist at configure time. Comment: It should be easy to check at configure time if all the dirs we will need actually exist. If they do not exist it's a good indication of a mistake. Should these be warnings or errors? To help with the misunderstanding in the original example perhaps the warning message should mention that paths with spaces need to use ""s. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/177#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects

#177: Check Include-dirs, extra-lib-dirs etc exist at configure time. ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: easy (<4 hours) Ghcversion: 6.6 | Platform: Windows ----------------------------+----------------------------------------------- Comment (by duncan): We now check that relative paths do exist, eg: {{{ include-dir: include }}} But we do not check absolute paths. The rationale is that relative paths are part of the package so if they're missing then we have a problem, but absolute paths are on the system and these might be just a list of possible paths that may exist on some systems and not others. Incidentally this would help in the original complaint {{{ include-dirs: C:\Program Files\PostgreSQL\8.2\include, C:\Program Files\PostgreSQL\8.2\include\server, . extra-lib-dirs: C:\Program Files\PostgreSQL\8.2\include, C:\Program Files\PostgreSQL\8.2\include\server }}} We would get a warning: {{{ Warning: 'include-dirs: Files\PostgreSQL\8.2\include' directory does not exist. Warning: 'include-dirs: Files\PostgreSQL\8.2\include\server' directory does not exist. Warning: 'extra-lib-dirs: Files\PostgreSQL\8.2\include' directory does not exist. Warning: 'extra-lib-dirs: Files\PostgreSQL\8.2\include\server' directory does not exist. }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/177#comment:6 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects

#177: Check Include-dirs, extra-lib-dirs etc exist at configure time. ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: easy (<4 hours) Ghcversion: 6.6 | Platform: Windows ----------------------------+----------------------------------------------- Comment (by duncan): Module/file dependency analysis is not relevant (#15 and #159). That's a different kind of dependency. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/177#comment:8 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects

#177: Check Include-dirs, extra-lib-dirs etc exist at configure time. ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal library | Version: 1.2.2.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: Windows ----------------------------+----------------------------------------------- Changes (by duncan): * priority: normal => low * difficulty: easy (<4 hours) => normal * milestone: Cabal-1.6 => Comment: So I think the decision is that we should only require that relative paths exist, not absolute paths. Ticket #262 covers checking that libs, and headers can actually be found. We should check that the configure flags `--extra-lib-dirs=`, `--extra- include-dirs=` do point to directories that actually exist. The only other improvement we could make would be to somehow notice that joining two adjacent components of a directory field with a space form a valid absolute path that actually exists, when both components do not, and in such a case suggest that the user perhaps meant to use a path with an embedded space in which case they must use "" Haskell String syntax. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/177#comment:10 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects