This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
start:installation [2018/10/12 15:20] rslesinger [Installing from source tarball] |
start:installation [2018/10/12 15:20] rslesinger [Installing the development (unstable) version] |
||
---|---|---|---|
Line 84: | 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. |