Fix VS build for FAST when using IFX Complier#2742
Merged
deslaughter merged 1 commit intoOpenFAST:rc-4.0.3from Apr 8, 2025
Merged
Fix VS build for FAST when using IFX Complier#2742deslaughter merged 1 commit intoOpenFAST:rc-4.0.3from
deslaughter merged 1 commit intoOpenFAST:rc-4.0.3from
Conversation
…tion build dependencies instead.
This was
linked to
issues
Apr 8, 2025
andrew-platt
approved these changes
Apr 8, 2025
Collaborator
andrew-platt
left a comment
There was a problem hiding this comment.
Checking with ifort now.
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
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.
PR is ready to merge.
Feature or improvement description
This PR corrects an issue when building the FAST VS Solution in Release_x86 which failed due to missing files from the MAP library when using the Intel IFX compiler. The issue seemed to be caused by including
MAP_*as an additional dependency instead of a build dependency, which made the paths to the object files wrong.Related issue, if one exists
Resolves #2725 and #2539
Impacted areas of the software
Visual Studio Project and Solution Files