faq.rst 1.3 KB

12345678910111213141516171819202122232425
  1. FAQs
  2. ====
  3. Building on other platforms
  4. ---------------------------
  5. NSIS can run on Linux, so you can build Windows installers without running
  6. Windows. However, if your package relies on compiled extension modules, like
  7. PyQt4, lxml or numpy, you'll need to ensure that the installer is built with
  8. Windows versions of these packages. There are two ways to do this:
  9. - Get the importable packages/modules, either from a Windows installation, or
  10. by extracting them from an installer. Copy them into a folder called
  11. ``pynsist_pkgs``, next to your ``installer.cfg`` file. pynsist will
  12. copy everything in this folder to the build directory.
  13. - Include exe/msi installers for those modules, and modify the ``.nsi`` template
  14. to extract and run these during installation. This can make your installer
  15. bigger and slower, and it may create unwanted start menu shortcuts
  16. (e.g. PyQt4 does), so the first option is usually better. However, if the
  17. installer sets up other things on the system, you may need to do this.
  18. When running on non-Windows systems, pynsis will bundle a 32-bit version of
  19. Python by default, though you can override this :ref:`in the config file <cfg_python>`.
  20. Whichever method you use, compiled libraries must have the same bit-ness as
  21. the version of Python that's installed.