Skip to content

Conversation

@JupiterRider
Copy link
Contributor

This should solve #409

@eXpl0it3r
Copy link
Member

Just changing the runtime linkage for CSFML won't help, as SFML also would rely on the runtime. But we intentionally prevent the static linking of the runtime when building SFML or CSFML as shared library, because you'd otherwise include a different version of the runtime in each SFML module DLL. For CSFML that would duplicate everything again, i.e. each CSFML and each SFML DLL would contain its own version of the runtime. This will eventually cause issues at the boundaries.

In the past we would link SFML statically into CSFML, but this then causes issues with singletons, see #136 (comment)

I guess the solution would be the package the runtime into the NuGet as well, given that Microsoft doesn't seem to offer an "install runtime" option for NuGet, nor do they provide the runtime as NuGet package.

@JupiterRider
Copy link
Contributor Author

I cam closing this in favor of #412

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