MacOS make generate
fix - regenerate certain mocks using source mode instead of reflect mode
#3886
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.
Which issue this PR addresses:
No Jira
What this PR does / why we need it:
I found after updating my OS to Sonoma 14.7, which included updating the Command Line Tools for Xcode from 15.3 to 16.0, that
make generate
was failing for certain packages and was also outputting some linker warnings. I can't explain exactly why it works, but I found that havingmockgen
use source mode instead of reflect mode for the failing packages fixed things. The linker warnings about a deprecated-ld_classic
, which were noted in the CLT for Xcode 16.0 release notes, also went away, which is interesting to note.I could try to dig into the reasoning for this change further, but I don't think it'd be a great use of time.
I've encountered multiple issues related to reflect mode in my work recently, which makes me wonder if we should switch to using source mode throughout the repository.
Test plan for issue:
Tested locally to confirm that it fixes
make generate
on my Mac and unit test still work, and then ranmake ci-rp
to make sure it didn't break anything in the containerized process either.Is there any documentation that needs to be updated for this PR?
N/A
How do you know this will function as expected in production?
Not a production change; only affects generation of mock interfaces that are used in unit tests.