➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lakor64
Recipients lakor64, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-05-10.11:27:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620646078.98.0.57549919171.issue44101@roundup.psfhosted.org>
In-reply-to
Content 
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.
History
Date User Action Args
2021-05-10 11:27:59lakor64setrecipients: + lakor64, paul.moore, tim.golden, zach.ware, steve.dower
2021-05-10 11:27:58lakor64setmessageid: <1620646078.98.0.57549919171.issue44101@roundup.psfhosted.org>
2021-05-10 11:27:58lakor64linkissue44101 messages
2021-05-10 11:27:58lakor64create