Closed Bug 496535 Opened 16 years ago Closed 14 years ago

Add pywin32 extensions to MozillaBuild

Categories

(Firefox Build System :: MozillaBuild, task)

x86
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rain1, Assigned: ted)

References

Details

pywin32 is required for getting stuff like Mozmill to work on Windows. The problem with installing the extensions separately is that the installer looks for Python registry entries, and we don't add them with MozillaBuild. It'd be great if we just included them, thus side-stepping the problem entirely.
This is a real pain in the ass to do as part of the MozillaBuild build. The pywin32 installer doesn't have any sort of silent mode, and by default it autodetects the system Python and not the one in the staging directory that winds up as part of the MozillaBuild package. I tried the trick mhammond suggested here: http://mail.python.org/pipermail/python-win32/2009-January/008629.html but couldn't get it to work.
Ok, I think I got it. Testing a patch now.
Assignee: nobody → ted.mielczarek
It looked like it installed, but it definitely doesn't work. I get "Entry point not found" dialogs complaining about things missing from pywintypes25.dll.
So yeah...the PyWin32 installer sticks stuff in windows/system32, which of course we don't package with MozillaBuild. I'm not about to make the MozillaBuild installer stick those files in windows/system32, either, so I think this is going to be WONTFIX. If you can figure out a way to make this work without needing those files in system32, then we can reopen and do it.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
We want to try to get rid of pywin32 in bug 507300. I hope it will be possible. Having a way to run Mozmill from within the Mozilla Build system would be great.
Re-opening at Ted's suggestion. Turns out some releng tools also need the pywin32 extensions. We're pretty sure we don't need the bits that end up in windows/system32 tough.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Right, I talked to mhammond about this a while ago, and he said the files in windows/system32 are only necessary for implementing COM components in Python or something like that, so we can get away without them.
I believe the patch I submitted to bug 580774 can help resolving this issue.
(In reply to Burak Yiğit Kaya from comment #9) > I believe the patch I submitted to bug 580774 can help resolving this issue. Sorry, I meant bug 673132
Blocks: 724191
So, we aren't using pywin32 anymore in mozmill, and I'd like to remove the entire dependency that talos has on pywin32 as well. If we do that, is there any need to bother with putting pywin32 into mozilla-build?
No
(In reply to Benjamin Smedberg [:bsmedberg] from comment #12) > No Great, then for clarity's sake I'll dupe this bug over to the remove pywin32 bug.
Status: REOPENED → RESOLVED
Closed: 16 years ago14 years ago
Resolution: --- → DUPLICATE
It's not exactly a dupe but a wontfix for mozilla build.
Resolution: DUPLICATE → WONTFIX
Product: mozilla.org → Firefox Build System
You need to log in before you can comment on or make changes to this bug.