Refs #4: Workaround invalid path generation in hsc2hs/inline-c on Windows #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-c on Windows This is a temporary hack to work around the invalid output paths generated by inline-c on Windows platforms: when hsc2hs and inline-c are used together in the same source file under Windows, Template Haskell yields source file names with all backslashes removed. See: fpco/inline-c#50 https://ghc.haskell.org/trac/ghc/ticket/12504
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since this is likely a bug in one of hsc2hs, inline-c or Template Haskell, it may take a while for a fix to be available. This temporary workaround will allow clang-pure to reference the inline-c-generated source file from its current, invalid location when building under Windows.