Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix MinGW compilation error because of new library ABI #74

Closed
wants to merge 1 commit into from

Conversation

ark0f
Copy link

@ark0f ark0f commented May 1, 2020

@ark0f ark0f force-pushed the mingw-compilation-fix branch from 117ed3a to c1fad17 Compare May 1, 2020 13:44
@@ -33,6 +36,9 @@ fn build_shaderc(shaderc_dir: &PathBuf, use_ninja: bool) -> PathBuf {
.define("SPIRV_WERROR", "OFF")
.define("SHADERC_SKIP_TESTS", "ON")
.define("CMAKE_INSTALL_LIBDIR", "lib");
if target_os == "windows" && target_env == "gnu" {
config.define("_GLIBCXX_USE_CXX11_ABI", "0");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks for the patch. I'm not very familiar with the MinGW environment. So MinGW actually uses the old ABI? Is this safe if they later change to the new ABI? Is there a way to detect which ABI to use?

It would be nice to paste the link here as a comment so folks can easily discover the reason of this definition. :)

@ark0f
Copy link
Author

ark0f commented May 2, 2020

Ah, actually this PR doesn't solve the problem and I don't know how to fix it. Sorry for wasted time.

I opened issue to understand what problem is: #75

@ark0f ark0f closed this May 2, 2020
@ark0f ark0f deleted the mingw-compilation-fix branch May 2, 2020 19:44
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