|
- Timestamp:
-
Feb 13, 2015, 11:38:30 AM (10 years ago)
- Author:
-
jweil
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v20
|
v21
|
|
1 | 1 | [[TOC(WikiStart,releaseNotes,windows,depth=2)]] |
| 2 | |
2 | 3 | = Running GiBUU on a Windows System = |
3 | 4 | |
4 | | == Step 1: Downloading the code == |
| 5 | Currently the recommended way of using GiBUU on a Windows system is via Cygwin. |
5 | 6 | |
6 | | === For normal users === |
7 | | 1. [wiki:GiBUUDownload#Gettingfullaccess Get your login account] or just [/login login]. |
8 | | 2. Download the [/browser/releases/ tar-ball] to your system. |
9 | | * Please take care, that the path where you store the tar-ball does not include blanks. |
10 | | * Especially "C:\Dokumente und Einstellungen\..." is no good, but "C:\work\" is fine! |
| 7 | == Cygwin == |
| 8 | |
| 9 | 1. Download [http://www.cygwin.com/ cygwin] |
| 10 | 2. Setup cygwin. In the package selection choose additionally: |
| 11 | * devel/gcc4-fortran |
| 12 | * devel/make |
| 13 | * devel/subversion |
| 14 | * utils/which |
| 15 | * utils/bzip2 |
| 16 | * libs/libbz2-devel |
| 17 | * perl/perl |
| 18 | 3. After the installation finished, start cygwin. |
| 19 | 4. Create a directory for GiBUU, e.g.: |
| 20 | {{{ |
| 21 | cd /cygdrive/c |
| 22 | mkdir GiBUU |
| 23 | cd GiBUU |
| 24 | }}} |
| 25 | 5. Checkout out the GiBUU code using svn, as explained in [wiki:svn]. |
| 26 | 6. Go to the directory "workingCode" (or "release1.x") and type |
| 27 | {{{ |
| 28 | make |
| 29 | }}} |
| 30 | 6. After make is done, you will find the executable "GiBUU.x" in the "testRun" directory, where you can run GiBUU with the command |
| 31 | {{{ |
| 32 | ./GiBUU.x < jobCardName |
| 33 | }}} |
| 34 | Sample jobcards are available in testRun/jobCards, cf. also [wiki:FAQ our FAQ page] for more informations. |
| 35 | |
| 36 | |
| 37 | |
| 38 | == Alternative checkout via TortoiseSVN / Putty == |
| 39 | |
| 40 | [http://tortoisesvn.tigris.org/ TortoiseSVN] is a nice GUI tool that integrates with the Windows Explorer. It can also be used to checkout the GiBUU code. However, this is currently not recommended, since it can potentially lead to file-permission problems in Cygwin. |
11 | 41 | |
12 | 42 | === For GiBUU developers === |
13 | | |
| 43 | |
| 44 | You can do the following to check out the code via svn+ssh with Cygwin (using ssh keys to avoid typing passwords all the time). |
| 45 | |
14 | 46 | See [http://tortoisesvn.net/ssh_howto.html TortoiseSVN SSH HowTo] or follow the explanation given below: |
15 | 47 | |
… |
… |
|
56 | 88 | 5. Click on "ok", and then "yes" to create the checkout directory. |
57 | 89 | |
58 | | |
59 | | == Step 2: Compiling & Running GiBUU == |
60 | | === Using Cygwin === |
61 | | 1. Download [http://www.cygwin.com/ cygwin] |
62 | | 2. Setup cygwin. In the package selection choose additionally: |
63 | | * devel/gcc4-fortran |
64 | | * devel/make |
65 | | * devel/subversion |
66 | | * utils/which |
67 | | * utils/bzip2 |
68 | | * libs/libbz2-devel |
69 | | * perl/perl |
70 | | 3. After the installation finished, start cygwin. |
71 | | 4. Now go to the GiBUU directory |
72 | | * If you downloaded the tar ball, change to the download directory (e.g. |
73 | | {{{ |
74 | | cd /cygdrive/c/work |
75 | | }}} |
76 | | Now unpack the tar-ball |
77 | | {{{ |
78 | | tar -xzf tarballName.tgz |
79 | | }}} |
80 | | * If you used svn to get the code, then simply "cd" to the code directory, e.g. |
81 | | {{{ |
82 | | cd /cygdrive/c/GiBUU |
83 | | }}} |
84 | | 5. Go to the directory "workingCode" (or "release1.x.x") and type |
85 | | {{{ |
86 | | make |
87 | | }}} |
88 | | 6. After make is done, you will find the executable "GiBUU.x" in the "testRun" directory, where you can run GiBUU with the command |
89 | | {{{ |
90 | | ./GiBUU.x < jobCardName |
91 | | }}} |
92 | | Sample jobcards are available in testRun/jobCards, cf. also [wiki:FAQ our FAQ page] for more informations. |
93 | | |
94 | | === In a terminal === |
95 | | Download your code to a network share, which is also accessible by some linux client. Go via putty to your linux client and compile the code as explained in "Readme_Quickstart.txt".[[BR]] |
96 | | |
97 | | '''Advantage:''' Much faster compilation and better performance than Cygwin. |
|