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

Reason for erroring out with posix threads? #61

Closed
alvinhochun opened this issue Apr 8, 2022 · 2 comments
Closed

Reason for erroring out with posix threads? #61

alvinhochun opened this issue Apr 8, 2022 · 2 comments

Comments

@alvinhochun
Copy link
Contributor

I see that f3ff9b5 added an error when the toolchain uses posix threads. What is the reasoning behind this?

@jrfonseca
Copy link
Owner

I don't want DrMinGW accidentally built with posix threads. At very least, posix threads would add one extra DLL dependency, a dependency that would need to be documented and redistributed, and I don't want that.

I'll add a comment to this effect.

As general rule, there are many ways one could try to build DrMinGW (with MSVC, Cygwin, MSYS, etc), but since DrMingw is distributed primarily as executable binaries. These create different challenges. So I prefer to have only one method to build allowed/supported.

@alvinhochun
Copy link
Contributor Author

I see. We build DrMingw with Krita for getting crash backtraces using exchndl.dll, so we ship all runtime DLLs anyway and this is not a problem for us. It would be nice if this check can be ignored by an option.

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

No branches or pull requests

2 participants