You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
include-dirs: C:\Program Files\MySQL\MySQL Server 5.6\include
extra-lib-dirs: C:\Program Files\MySQL\MySQL Server 5.6\lib
in my cabal file, it will fail with errors such as Warning: 'include-dirs: 5.6\include' directory does not exist., which looks like the paths are being split on spaces. I've tried adding double quotes around them, but the same thing happens.
I couldn't really find if there's another syntax for specifying paths like this, and I tried cabal-install 1.18 and 1.22, both with the same effect, which is why I'm opening the issue in the cabal repo itself. I've also tried escaping the spaces with \\, but that didn't seem to help either.
The text was updated successfully, but these errors were encountered:
@darthdeus .cabal files can use Haskell string syntax for these cases. So in this case that means using "" and escaping the '' chars (or using '/' instead).
include-dirs: "C:\\Program Files\\MySQL\\MySQL Server 5.6\\include"
extra-lib-dirs: "C:\\Program Files\\MySQL\\MySQL Server 5.6\\lib"
FYI, this has been the case since pre-1.0 and is documented in the user guide.
Plausibly we could somehow try and warn about this mistake and suggest the correct solution, i.e. string syntax.
If I add one of the following
in my cabal file, it will fail with errors such as
Warning: 'include-dirs: 5.6\include' directory does not exist.
, which looks like the paths are being split on spaces. I've tried adding double quotes around them, but the same thing happens.I couldn't really find if there's another syntax for specifying paths like this, and I tried
cabal-install
1.18 and 1.22, both with the same effect, which is why I'm opening the issue in the cabal repo itself. I've also tried escaping the spaces with\\
, but that didn't seem to help either.The text was updated successfully, but these errors were encountered: