Including PYDs/DLLs in py2exe builds

Question

One of the modules for my app uses functions from a .pyd file. There's an option to exclude dlls (exclude_dlls) but is there one for including them? The build process doesn't seem to be copying the .pyd in my module despite copying the rest of the files (.py). I also need to include a .dll. How do I get py2exe to include both .pyd and .dll files?

Answer 1

If they're not being automatically detected, try manually copying them into py2exe's temporary build directory. They will be included in the final executable.

Answer 2

You can modify the setup script to copy the files explicitly:

script = "PyInvaders.py"     #name of starting .PY
project_name = os.path.splitext(os.path.split(script)[1])[0]
setup(name=project_name, scripts=[script]) #this installs the program

#also need to hand copy the extra files here
def installfile(name):
    dst = os.path.join('dist', project_name)
    print 'copying', name, '->', dst
    if os.path.isdir(name):
 dst = os.path.join(dst, name)
 if os.path.isdir(dst):
     shutil.rmtree(dst)
 shutil.copytree(name, dst)
    elif os.path.isfile(name):
 shutil.copy(name, dst)
    else:
 print 'Warning, %s not found' % name

pygamedir = os.path.split(pygame.base.__file__)[0]
installfile(os.path.join(pygamedir, pygame.font.get_default_font()))
installfile(os.path.join(pygamedir, 'pygame_icon.bmp'))
for data in extra_data:
    installfile(data)

etc... modify to suit your needs, of course.

Answer 3

Maybe you could use the data_files option to setup():

import glob
setup(name='MyApp',
      # other options,
      data_files=[('.', glob.glob('*.dll')),
                  ('.', glob.glob('*.pyd'))],
     )

data_files should be a list of tuples, where each tuple contains:

1. The target directory.
2. A list of files to copy.

This won't put the files into library.zip, which shouldn't be a problem for dlls, but I don't know about pyd files.

Answer 4

i'm reasonably confident that there are better tools than py2exe for this job, that would habdle all this stuff behind the scenes. a search on SO would probably reveal.

Answer 5

.pyd's and .DLL's are different here, in that a .pyd ought to be automatically found by modulefinder and so included (as long as you have the appropriate "import" statement) without needing to do anything. If one is missed, you do the same thing as if a .py file was missed (they're both just modules): use the "include" option for the py2exe options.

Modulefinder will not necessarily find dependencies on .DLLs (py2exe can detect some), so you may need to explicitly include these, with the 'data_files' option.

For example, where you had two .DLL's ('foo.dll' and 'bar.dll') to include, and three .pyd's ('module1.pyd', 'module2.pyd', and 'module3.pyd') to include:

setup(name='App',
      # other options,
      data_files=[('.', 'foo.dll'), ('.', 'bar.dll')],
      options = {"py2exe" : {"include" : "module1,module2,module3"}}
     )