Don't generate .pc files for MSVC compatible tool chains. #382
Conversation
This file contains 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
|
Yes - that would be a good idea if they're not needed for MSVC. Thanks. We can add this to SuiteSparse v7.2.0. |
DrTimothyAldenDavis
merged commit 0dd6e8f
into
DrTimothyAldenDavis:dev2
15 checks passed
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.
The flags in the generated pkg-config files are incompatible with MSVC-compatible tool chains.
While it is very uncommon for MSVC-compatible tool chains to use .pc files at all, it would be better to not generate these files for those tool chains at all.
The proposed changes skip generating the .pc files when using a MSVC-compatible tool chain.
It would be nice if this could still be included in SuiteSparse 7.2.0.