Skip to content

fix compilation in vs2025#641

Merged
NotRequiem merged 1 commit intokernelwernel:mainfrom
movqword:main
Feb 26, 2026
Merged

fix compilation in vs2025#641
NotRequiem merged 1 commit intokernelwernel:mainfrom
movqword:main

Conversation

@movqword
Copy link
Contributor

MAKE SURE TO READ THE CONTRIBUTION GUIDELINES BEFORE CONTINUING!


What does this PR do?

  • Add a new technique
  • Add a new feature
  • Add a new README translation
  • Improve code
  • Fix bugs
  • Refactoring or code organisation
  • Stylistic changes
  • Sync between branches
  • Other

Briefly explain what this PR does:

Compilation error in Visual Studio 2025 (C++17, v143)

1>Source\ThirdParty\Include\vmaware.hpp(11030,40): error C3493: 'VID_INTEL' cannot be passed implicitly because no default transfer mode is specified
1>Source\ThirdParty\Include\vmaware.hpp(11031,45): error C3493: 'VID_AMD_ATI' cannot be passed implicitly because no default transfer mode is specified
1>Source\ThirdParty\Include\vmaware.hpp(11031,67): error C3493: 'VID_AMD_MICRO' cannot be passed implicitly because no default transfer mode is specified default
1>Source\ThirdParty\Include\vmaware.hpp(11061,33): error C2064: fragment does not evaluate to a function that takes 0 arguments
1>Source\ThirdParty\Include\vmaware.hpp(11061,24): error C2737: "vendor": const object must be initialized

@NotRequiem NotRequiem merged commit d662c6a into kernelwernel:main Feb 26, 2026
2 checks passed
@NotRequiem
Copy link
Collaborator

thank you! :)

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.

2 participants