deployment

[coldfix]

The problem: madgui depends on a built version of MAD-X and PyMAD. Therefore, at least a working C-compiler is required when building the application. For windows systems this is a non-trivial requirement. It is therefore desirable to have the possibility to distribute built versions of these dependencies. Since binary versions are prone not to work with python interpreters of different versions the required python interpretor should be delivered with the product.

Suggested solution [obsolete]: This means that the installer should come with a ready-to-use virtualenv egg and should install into a virtualenv. If a relocatable installed version can be achieved no installer will be required.

• use buildout to download and build all components
• create binary versions of the components with wheel
• store built versions of the dependencies in a local folder of a relocatable virtualenv for use with offline-bootstrap.py
• create a setup script that invokes buildout such that it uses the built cache and does not build from the internet
• Using buildout system on windows
• Install wxPython in buildout

Scrub that, buildout sucks.

New suggested solution:

• put eggs of all dependencies in a folder
• have a run script in top level folder
• add eggs to working set, see also here
• not sure how to get virtualenv easily

[coldfix]

Where source modifications are uncommon (at control system PCs?), a valid option is to use freezers. For windows, there is:

• py2exe
• cx_Freeze
• PyInstaller
• bbfreeze

See also: Distribution Utilities

[coldfix]

Any wheel based installation method is now easy enough.