Who uses libpython38.a on Windows?

One of the most annoying steps in building the Windows installers is generating the libpython38.a file. It's annoying, because it requires having "generic enough" MinGW tools to ensure that the file is compatible with whatever version of MinGW might be trying to build against the regular Windows distribution.
I would like to stop shipping this file in 3.8 and instead put the steps into the docs to show people how to generate them themselves (with the correct version of their tools):
gendef python38.dll > tmp.def dlltool --dllname python38.dll --def tmp.def --output-lib libpython38.a -m i386:x86-64
(Obviously the commands themselves are not complicated if you already have gendef and dlltool, but currently a normal CPython build system does not have these.)
Before just doing this, I wanted to put out a request for information:
* Do you rely (or know anyone who relies) on libpython38.a on Windows? * Are you able to add the two commands above to your build? If not, why not?
Thanks, Steve

On 2019-06-14 21:53, Steve Dower wrote:
One of the most annoying steps in building the Windows installers is generating the libpython38.a file. It's annoying, because it requires having "generic enough" MinGW tools to ensure that the file is compatible with whatever version of MinGW might be trying to build against the regular Windows distribution.
I would like to stop shipping this file in 3.8 and instead put the steps into the docs to show people how to generate them themselves (with the correct version of their tools):
gendef python38.dll > tmp.def dlltool --dllname python38.dll --def tmp.def --output-lib libpython38.a -m i386:x86-64
(Obviously the commands themselves are not complicated if you already have gendef and dlltool, but currently a normal CPython build system does not have these.)
Before just doing this, I wanted to put out a request for information:
- Do you rely (or know anyone who relies) on libpython38.a on Windows?
- Are you able to add the two commands above to your build? If not, why not?
I'm able to build the regex module without it; in fact, I believe I've been able to do so since Python 3.5!

On 14Jun2019 1930, MRAB wrote:
I'm able to build the regex module without it; in fact, I believe I've been able to do so since Python 3.5!
This is about the only specific feedback I've received (including on Twitter, where most reactions were "I have no idea what file you're talking about"), so I'm going to drop the MinGW lib from 3.8 and update the docs with instruction.
Cheers, Steve

ok.
currently it has develop for web, ML, scripting, edu. how about another box: "Building apps for Windows using Python"... is that a reality yet?
Sent from Outlookhttp://aka.ms/weboutlook
________________________________ From: Steve Dower steve.dower@python.org Sent: Friday, June 14, 2019 1:53 PM To: Python Dev Subject: [Python-Dev] Who uses libpython38.a on Windows?
One of the most annoying steps in building the Windows installers is generating the libpython38.a file. It's annoying, because it requires having "generic enough" MinGW tools to ensure that the file is compatible with whatever version of MinGW might be trying to build against the regular Windows distribution.
I would like to stop shipping this file in 3.8 and instead put the steps into the docs to show people how to generate them themselves (with the correct version of their tools):
gendef python38.dll > tmp.def dlltool --dllname python38.dll --def tmp.def --output-lib libpython38.a -m i386:x86-64
(Obviously the commands themselves are not complicated if you already have gendef and dlltool, but currently a normal CPython build system does not have these.)
Before just doing this, I wanted to put out a request for information:
* Do you rely (or know anyone who relies) on libpython38.a on Windows? * Are you able to add the two commands above to your build? If not, why not?
Thanks, Steve _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.pytho... Message archived at https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.pytho...

oops, apologies - pls ignore 🙂.
Sent from Outlookhttp://aka.ms/weboutlook
________________________________ From: Shahrokh Mortazavi Sent: Tuesday, June 18, 2019 2:16 PM To: Steve Dower; Python Dev Subject: Re: [Python-Dev] Who uses libpython38.a on Windows?
ok.
currently it has develop for web, ML, scripting, edu. how about another box: "Building apps for Windows using Python"... is that a reality yet?
Sent from Outlookhttp://aka.ms/weboutlook
________________________________ From: Steve Dower steve.dower@python.org Sent: Friday, June 14, 2019 1:53 PM To: Python Dev Subject: [Python-Dev] Who uses libpython38.a on Windows?
One of the most annoying steps in building the Windows installers is generating the libpython38.a file. It's annoying, because it requires having "generic enough" MinGW tools to ensure that the file is compatible with whatever version of MinGW might be trying to build against the regular Windows distribution.
I would like to stop shipping this file in 3.8 and instead put the steps into the docs to show people how to generate them themselves (with the correct version of their tools):
gendef python38.dll > tmp.def dlltool --dllname python38.dll --def tmp.def --output-lib libpython38.a -m i386:x86-64
(Obviously the commands themselves are not complicated if you already have gendef and dlltool, but currently a normal CPython build system does not have these.)
Before just doing this, I wanted to put out a request for information:
* Do you rely (or know anyone who relies) on libpython38.a on Windows? * Are you able to add the two commands above to your build? If not, why not?
Thanks, Steve _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.pytho... Message archived at https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.pytho...
participants (3)
-
MRAB
-
Shahrokh Mortazavi
-
Steve Dower