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:17] rslesinger [Installing from source tarball] |
start:installation [2018/10/12 15:22] rslesinger [Download] |
||
---|---|---|---|
Line 4: | Line 4: | ||
==== Download ==== | ==== Download ==== | ||
- | GSvit can be downloaded as stable version, which is recommended, either as binary | + | GSvit can be downloaded as stable version, which is recommended, either as a Windows binary installer or as source code. A current development version can be also obtained from Subversion repository, however this is not recommended as code under development might behave unexpectedly. |
- | package for many different operating systems or as source code. A current development | + | |
- | version can be also obtained from Subversion repository, however this is not recommended | + | |
- | as code under development might behave unexpectedly. | + | |
- | See [[http://gsvit.net/download.php|GSvit download pages]] for more details. | + | |
+ | Download links can be found at [[http://gsvit.net/download.php|GSvit download pages]]. | ||
==== Binary installation ==== | ==== Binary installation ==== | ||
Line 54: | Line 50: | ||
</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 57: | ||
== 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 84: | Line 80: | ||
''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. |