User Tools
start:installation
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
start:installation [2018/10/12 15:16] rslesinger [Binary installation] |
start:installation [2018/10/12 15:20] rslesinger [Installing the development (unstable) version] |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| </code> | </code> | ||
| - | You can specify the path where to install GSvit by a configure option ''--prefix=path''. | + | You can specify the path where to install GSvit by a configure option ''%%--%%prefix=path''. |
| A binary RPM can also be built from the source code tarball directly by issuing the following command: | A binary RPM can also be built from the source code tarball directly by issuing the following command: | ||
| Line 61: | Line 61: | ||
| == Using a non-packaged CUDA installation == | == Using a non-packaged CUDA installation == | ||
| - | The //PATH// variable is used to search for Nvidia's compiler NVCC. In order to find it, you need to set this variable accordingly, e.g. ''export PATH=/usr/local/cuda-X.Y/bin:$PATH''. Alternatively, you can provide path by option ''--with-cuda=path'' to ''./configure''. | + | The //PATH// variable is used to search for Nvidia's compiler NVCC. In order to find it, you need to set this variable accordingly, e.g. ''export PATH=/usr/local/cuda-X.Y/bin:$PATH''. Alternatively, you can provide path by option ''%%--%%with-cuda=path'' to ''./configure''. |
| Please don't forget to adjust also your //LD_LIBRARY_PATH// variable, e.g. by ''export LD_LIBRARY_PATH=/usr/local/cuda-X.Y/lib64:/usr/local/cuda-X.Y/lib:$LD_LIBRARY_PATH''. Or you can update the ''/etc/ld.so.conf'' file to contain the CUDA lib directory, however this needs root's permissions. | Please don't forget to adjust also your //LD_LIBRARY_PATH// variable, e.g. by ''export LD_LIBRARY_PATH=/usr/local/cuda-X.Y/lib64:/usr/local/cuda-X.Y/lib:$LD_LIBRARY_PATH''. Or you can update the ''/etc/ld.so.conf'' file to contain the CUDA lib directory, however this needs root's permissions. | ||
| Line 67: | Line 67: | ||
| == Gwyddion == | == Gwyddion == | ||
| - | You also need to have Gwyddion open source software installed to provide output to .gwy files. If you installed Gwyddion in a nonstandard location, you have to set up the //PKG_CONFIG_PATH// variable, e.g. by ''export PKG_CONFIG_PATH=/home/username/somedir/gwyddion-X.Y/lib/pkgconfig:$PKG_CONFIG_PATH''. | + | GSvit is also dependent on Gwyddion's libraries, so you need first to install this software. You can download and install it using procedures described on the official [[http://gwyddion.net/download.php|Gwyddion download]]. You also need to have Gwyddion open source software installed to provide output to .gwy files. |
| + | |||
| + | If you installed Gwyddion in a nonstandard location, you have to set up the //PKG_CONFIG_PATH// variable, e.g. by ''export PKG_CONFIG_PATH=/home/username/somedir/gwyddion-X.Y/lib/pkgconfig:$PKG_CONFIG_PATH''. | ||
| The software has primarily been tested on openSUSE, Fedora and Debian, but hopefully should run on any system with CUDA and Gwyddion. | The software has primarily been tested on openSUSE, Fedora and Debian, but hopefully should run on any system with CUDA and Gwyddion. | ||
| Line 82: | Line 84: | ||
| ''svn checkout svn:%%//%%svn.code.sf.net/p/gsvit/code/trunk gsvit''. For Windows, we have good experience with TortoiseSVN as a Subversion client. | ''svn checkout svn:%%//%%svn.code.sf.net/p/gsvit/code/trunk gsvit''. For Windows, we have good experience with TortoiseSVN as a Subversion client. | ||
| - | Under Linux environment the software should be installed using the standard source installation procedure, except ''./configure'' is replaced by ''./autogen.sh''. Note that you can also pass arguments such as ''--prefix=path''. | + | Under Linux environment the software should be installed using the standard source installation procedure, except ''./configure'' is replaced by ''./autogen.sh''. Note that you can also pass arguments such as ''%%--%%prefix=path''. |
| Under Windows environment we use MS Visual Studio 2015, and we can provide a solution and project files together with all the necessary dependencies upon request. This MSVC version is able to compile 64-bit binaries, and indeed we succeded to complete the build. However, the 64-bit XSvit binary behaves oddly so we decided not to publish GSvit-x64 for now. We plan to put these together with all dependencies in the svn repository. | Under Windows environment we use MS Visual Studio 2015, and we can provide a solution and project files together with all the necessary dependencies upon request. This MSVC version is able to compile 64-bit binaries, and indeed we succeded to complete the build. However, the 64-bit XSvit binary behaves oddly so we decided not to publish GSvit-x64 for now. We plan to put these together with all dependencies in the svn repository. | ||
start/installation.txt · Last modified: 2021/02/08 11:15 by pgrolich
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
