mirror of
https://github.com/ultimatepp/ultimatepp.git
synced 2026-05-15 14:16:07 -06:00
[GH-ISSUE #301] Strange Assist++ error on Windows when MSVC as compiler is selected (Clang 21) #94
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/ultimatepp#94
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @klugier on GitHub (Oct 11, 2025).
Original GitHub issue: https://github.com/ultimatepp/ultimatepp/issues/301
Originally assigned to: @mirek-fidler on GitHub.
Hello, I replaced bin directory and libclang binaries to version 21.1 on Windows, but it looks like it generates scanning errors in the valid code. For example I have this issue in ide/BaseDlg.cpp, but other files are affected as well.
@mirek-fidler commented on GitHub (Oct 11, 2025):
Can you try with nightly build? (It is already updated to 21.1.1 / openssl 3.6.0)
Mirek
@ismail-yilmaz commented on GitHub (Oct 11, 2025):
21.1.1 works fine here:
@klugier commented on GitHub (Oct 11, 2025):
Thanks! I will do clean install.
@klugier commented on GitHub (Oct 19, 2025):
I am reopening this issue. It looks like when you select MSVC then these assist errors appears! FYI, @mirek-fidler. I think Assist++ should work the same whenever CLANG, GCC or MSVC is selected. If we don't fix it, then working with MSVC will be diffcult and not joyful.
@mirek-fidler commented on GitHub (Oct 19, 2025):
This does not have a good solution - CLANG is incompatible with Microsft SDK header files. I have fixed it by completely ignoring "real" build method and always using just CLANGx64 method for assist (I mean, to determine include path) to determine headers. Which has its flaws, but the best we can do now.
@klugier commented on GitHub (Oct 20, 2025):
I think it is a fair approach, if you want to have custom includes with MSVC just update Clang build method as well.