-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Unable to build C++ module as a shared library #2099
Comments
I might have just hit the same problem. Was following: Environment: The build spew a ton of unresolved external symbol error as following:
Since it is a dependency issue, I tried to comment out the following line from the tutorial:
Maybe the MSVC requires some additional flag to defer symbol resolution to runtime? |
Correction, by removing the dependency library list clean up, I was able to build the shared library, but not the engine tools executable. Latter failed with error:
|
Looks like there is something wrong around the following line also:
|
It seems that |
@akien-mga Applying the patch on top of On Still looking further. |
I think I am getting closer on this. The first problem is that MSVC linker do no take Now, according to scons docs
But as I check my build, the import (.lib) library is not built, thus the problem. |
Traced into |
Looks like reason of the missing "import" After fixing that, I am able to build dll for
However, this does break again once I try to build
(Building tools always have no problem because it does not support After sometime of investigation, I found this is due to the hard coded It looks like these options are added here solely for the executable, without taking Lastly, adding the following lines to SCsub would workaround the issue:
|
I can confirm this is still an issue in 3.2.3-stable |
Same thing. Still present at 3.4.2. |
Duplicate of godotengine/godot#15675. |
Been following the latest documentation and I cannot compile the engine and a custom C++ module as a shared library on Windows 10 with MSVC 2017.
The text was updated successfully, but these errors were encountered: