You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2021-05-10.11:27:58.956>labels= ['type-bug', 'OS-windows', '3.11']
title="Generation of an executable's library file when python is built is static"updated_at=<Date2021-05-10.11:27:58.956>user='https://github.com/lakor64'
When linking any windows application with pythoncore built as a static library, such executable will automatically export all python c api functions and generate a static library.
Exporting functions from a static library is a strange behavour, as I am not aware of any reason why dllimport/export should be used when building a static library.
This behavour oncurrs because python's export.h doesn't know when the library is linked as shared or static.
I have attached a patch that should fix this issue.
Tested under Windows 10 + VS2019, a static linkage of Python3 does not produce any library file anymore, and such exports are no longer visible with Dependencies.
I would like to apology if I got any tag wrong, as it's my first issue here.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
Linked PRs
The text was updated successfully, but these errors were encountered: