DLSS Enabler static-embedding compatibility #1035
Open
artur-graniszewski wants to merge 1 commit into
Open
Conversation
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.
Summary
Adds the ability to build OptiScaler as a static library and embed it into a
host DLL (e.g. DLSS Enabler), alongside the existing standalone DLL build.
All new behavior is gated behind the
OPTISCALER_STATICmacro and a dedicatedbuild configuration, so the default DLL build path is completely unaffected.
Changes
ReleaseStaticbuild configuration. Builds OptiScaler as a static.libwith the static CRT (
/MT) and definesOPTISCALER_STATIC. Because the CRT islinked statically, any static dependencies it pulls in (e.g. the FSR3 /
FidelityFX SDK) must be compiled in the same
/MTmode — mixing/MTand/MDwithin one module causes CRT symbol conflicts.
DllMaindemotion (static build only). UnderOPTISCALER_STATIC,DllMainis renamed to
org_dllMainvia a forced-include macro. It stops being the moduleentry point and becomes a regular function the host can call. In standard DLL
builds the macro is not defined, so
DllMainremains the entry point as before.OptiScaler_Init(HMODULE self, const OptiScalerConfig* cfg)and
OptiScaler_Shutdown()forward to the originalDllMainlogic withDLL_PROCESS_ATTACH/DLL_PROCESS_DETACH, preserving the existing init andcleanup paths. The host passes its own module handle for module-relative lookups.
OptiScalerConfigstruct for future use.host's own version-check code.