Improve support of clang #158
Open
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
MisterDA
force-pushed
the
clang-print-search-dirs
branch
11 times, most recently
from
4888cc4 to
b4a33c4
Compare
Record the compiler used during FlexDLL's build in a new module. In the case of MINGW* and CYGWIN64 toolchains, this allows using alternative compilers such as clang. Otherwise, FlexDLL would default to querying GCC, which may report different path list than clang. In the case of MSVC and MSVC64 toolchains, this allows using alternative compilers such as clang-cl. Otherwise, FlexDLL would default to using cl.exe, which may not be desired or even available.
`clang -print-search-dirs` doesn't print an `install` field and its `libraries` path list is already in mixed-style (Windows path with forward slashes separated by semicolons). This happens when using clang in both MSYS2 MINGW64 or CLANG64 environments. The `libraries` path list may also contain empty paths, strip them.
MisterDA
force-pushed
the
clang-print-search-dirs
branch
from
b4a33c4 to
52775f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm trying to use clang everywhere. The MSYS2 CLANG64 environment uses UCRT, but we're missing bits to link with it right now. It is however possible to use clang with MSYS2 MINGW64 environment, or with Cygwin+mingw, or with the MSYS2 MSYS and Cygwin+cygwin1.dll environments (although in this last two cases clang packages are currently unmaintained).
It is also possible to use clang-cl instead of MSVC.
This PR makes sure that flexlink doesn't default to GCC or MSVC when clang is desired instead.
The first step is to retain the compilers used when building for searching library directories. This allows using alternative compilers, otherwise, FlexDLL would default to querying GCC, which may report different path list than clang.
The second step teaches FlexDLL to parse clang's output.
clang.exe -print-search-dirsdoesn't print aninstallfield and itslibrariespath list is already in mixed-style (Windows path with forward slashes separated by semicolons). This happens when using clang in both MSYS2 MINGW64 or CLANG64 environments.