Skip to content

--include flag cannot handle windows paths #30

Closed
@ian-ross

Description

@ian-ross

Bug imported from C2HS Trac

Trac ticket created: 2010-05-03T10:48:19-0700


c2hs splits the string passed via the --include flag on the ':' character. On Unix, ':' is the search path separator character and the --include flag is intended to accept a whole search path in one go. On Windows, absolute paths look like c:\blah and these get broken if we split on ':' chars.

Also it gobbles spaces. That breaks windows paths that often use spaces.

Probably the solution is to use System.FilePath.splitSearchPath to split the search path. This uses ':' on Unix and ';' on Windows.

Should also double check the order/priority of multiple independent --include flags vs --include=first:second.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions