Skip to content

Conversation

@hwangsihu
Copy link
Contributor

No description provided.

@hwangsihu hwangsihu requested a review from bear101 as a code owner December 6, 2025 01:43
@hwangsihu hwangsihu requested a review from Copilot December 6, 2025 04:32
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@hwangsihu hwangsihu force-pushed the ltcg branch 2 times, most recently from 449be62 to 9a021a1 Compare December 8, 2025 00:23
@bear101
Copy link
Contributor

bear101 commented Dec 10, 2025

What exactly is the benefit of this change? When I look at the size of TeamTalk5.dll on main branch and ltcg branch then it's exactly the same.

@hwangsihu
Copy link
Contributor Author

What exactly is the benefit of this change? When I look at the size of TeamTalk5.dll on main branch and ltcg branch then it's exactly the same.

Sorry, I just checked.
When compiling most files, you'll see a warning message saying that using the /ltcg option will improve linker performance.
This is in response to the warning.

@bear101
Copy link
Contributor

bear101 commented Dec 14, 2025

Looking at the build times I don't see any improvements in build time compared to master branch

@hwangsihu
Copy link
Contributor Author

But wouldn't it be nice if we could get rid of the warning message?

@bear101
Copy link
Contributor

bear101 commented Dec 17, 2025

By default VS2022 sets Link Time Code Generation to nothing (blank) for Debug and /LTCG:incremental for Release builds on DLL projects.

@hwangsihu
Copy link
Contributor Author

hwangsihu commented Jan 11, 2026

@bear101 Ah, Did you mean to change /LTCG to /LTCG:incremental?

@hwangsihu hwangsihu changed the title Add /LTCG option Add /LTCG:incremental option Jan 11, 2026
@hwangsihu hwangsihu force-pushed the ltcg branch 2 times, most recently from 6701360 to ad4f698 Compare January 15, 2026 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants