-
Notifications
You must be signed in to change notification settings - Fork 341
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
Link errors on MinGW #31
Comments
It is possible to tell the linker (ld) which symbols to export I've tried it with a simple test lib and it seems to work under mingw. |
I thought this is what I was doing with |
Did you manage to build Atmosphere sample? |
Took me a bit of trial-and-error, but I've got it to run. There is another issue though. The samples using xinput don't link against it (-lxinput). |
This commit fixes compile errors. |
When building the engine on MinGW, some applications fail to link due to duplicate symbols coming from the import library, which makes no sense. The size of import libraries is ridiculous for DLLs exporting just one public symbol. Apparently there is an issue with the linker that adds a bunch of stuff to the import library even though all symbols are hidden.
https://stackoverflow.com/questions/54331717/duplicate-symbol-defined-in-a-dll-import-library-in-mingw-build
The text was updated successfully, but these errors were encountered: