2,684
edits
Installation: Difference between revisions
→Windows
| Line 200: | Line 200: | ||
== Windows == | == Windows == | ||
The programs of the XDS package as well as XDSGUI, XDSSTAT and so on may be run on 64bit Windows10 within the [http://www.pcworld.com/article/3050473/windows/heres-how-windows-10s-ubuntu-based-bash-shell-will-actually-work.html Linux Subsystem for Windows]. This installs a Ubuntu 14.04.5 LTS environment, which supports the apt package manager. | The programs of the [[XDS]] package as well as [[XDSGUI]], [[XDSSTAT]], [[XDSCC12]] and so on may be run on 64bit Windows10 within the [http://www.pcworld.com/article/3050473/windows/heres-how-windows-10s-ubuntu-based-bash-shell-will-actually-work.html Linux Subsystem for Windows]. This (easily!) installs a Ubuntu 14.04.5 LTS environment, which supports the apt package manager, so in principle anything can be installed. | ||
Graphical Linux programs require installation of a X server like [https://sourceforge.net/projects/xming/files/latest/download Xming] on the Windows host. To use it, one has to say in the shell window | Graphical Linux programs require installation of a X server like [https://sourceforge.net/projects/xming/files/latest/download Xming] on the Windows host. To use it, one has to say in the shell window | ||
export DISPLAY=:0 | export DISPLAY=:0 | ||
XDSGUI requires | before running the program. XDSGUI requires | ||
sudo apt-get install libgomp1 libqtgui4 | sudo apt-get install libgomp1 libqtgui4 | ||
and [[generate_XDS.INP]] requires a number of packages (some of which are only for specific detectors!); I'd start with | and [[generate_XDS.INP]] requires a number of packages (some of which are only for specific detectors!); I'd start with | ||
| Line 210: | Line 210: | ||
and if required, also install python and hdf5-tools. | and if required, also install python and hdf5-tools. | ||
Unfortunately, only single-processor xds runs smoothly, whereas the parallel xds_par stops with an error message. | Unfortunately, only single-processor xds runs smoothly, whereas the parallel xds_par stops with an error message. I did not yet investigate this, but there is a workaround: | ||
# since xds_par does not work anyway, just copy the xds binary over the xds_par binary so that it is available under both names | # since xds_par does not work anyway, just copy the xds binary over the xds_par binary so that it is available under both names (XDSGUI runs xds_par!) | ||
# in XDS.INP, specify MAXIMUM_NUMBER_OF_JOBS= <number of cores> | # in XDS.INP, specify MAXIMUM_NUMBER_OF_JOBS= <number of cores> | ||