From: Tony C. <cap...@gm...> - 2007-09-16 04:33:47
|
I ran a py2exe setup script at work and noticed that cygwin.dll was added to the final executable. It's not being used by anything I import- or anything that is being imported. When I run the same py2exe script on my home computer, which doesn't have cygwin installed, I have no problems making an executable. How cygwin even was referenced for this project is beyond me. So I've added an excludes statement to setup.py, but the cygwin.dll is still included. Is this normal behavior for py2exe? Does excluded absolutely (unconditionally) override any module that is explicitly imported? |
From: Thomas H. <th...@ct...> - 2007-09-17 15:05:30
|
Tony Cappellini schrieb: > I ran a py2exe setup script at work and noticed that cygwin.dll was > added to the final executable. > > It's not being used by anything I import- or anything that is being imported. > When I run the same py2exe script on my home computer, which doesn't > have cygwin installed, I have no problems making an executable. How > cygwin even was referenced for this project is beyond me. Can it be that cygwin.dll is pulled in by some binary dependency? Is there any extension (.dll or .pyd) that depends on cygwin.dll? > So I've added an excludes statement to setup.py, but the cygwin.dll is > still included. I think you should use the "dll-excludes" option. "excludes" is for Python modules. Thomas |