Changeset 11946
- Timestamp:
- 04/05/12 15:17:51 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
issm/trunk-jpl/externalpackages/windows/InstallInstructions.txt
r11926 r11946 19 19 Cygwin: 20 20 21 -You will need cygwin installed on your Windows platform to manage the compilation. 22 The compilation will still be carried out by the windows sdk compiler, but the 21 -You will need cygwin installed on your Windows platform to manage the compilation. Cygwin emulates 22 unix behaviour on windows machines. The compilation will still be carried out by the windows sdk compiler, but the 23 23 environment driving the compilation will be the unix-like cygwin. When you download 24 24 cygwin, make sure that you install it in the C:\Cygwin directory. … … 62 62 This is by far the most tricky part. 63 63 64 Follow Figure 2for more details. You have to launch sdk 7.1 command prompt, go to the64 Follow Sdk1.png and Sdk2.png for more details. You have to launch sdk 7.1 command prompt, go to the 65 65 cygwin directory and fire up Cygwin by executing Cygwin.bat. Once this is done,dump the 66 66 results of the export command onto a file, called sdk7.1.win7.64.sh … … 71 71 Downloading issm: 72 72 73 Download issm onto the C:\ directory. Do not download it in your Documents or Desktop73 Download issm into the C:\ directory. Do not download it in your Documents or Desktop 74 74 folder. 75 75 … … 103 103 cl hello.cpp 104 104 105 If this does not work, do not go any further! The settings of your cl compiler are found 106 in externalpackages/windows/configs/ 107 First, you can try updating the user-specific settings to refer to your username and then 108 trying to run cl hello.cpp again. 109 If there is still a significant different between your sdk7.1.win7.64.sh file (see above section Compiler) 110 and the file that is being sourced in the windows/configs directory, place your new file in 111 the configs directory. Relaunch bash, and try to run cl hello.cpp once more. Beware, you will likely 112 have to erase some lines in your file, as cygwin might not like some of the stuff that your 105 If this does not work, do not go any further! The settings of your cl compiler are found 106 in externalpackages/windows/configs/. If there is a significant different between your 107 sdk7.1.win7.64.sh file (see above section Compiler) and the file that is being sourced in the windows/configs directory, place your new file in 108 the configs directory. Relaunch bash, and try to run cl hello.cpp once more. Beware, you will likely 109 have to erase some lines in your file, as cygwin might not like some of the stuff that your 113 110 Windows platform is trying to define. To make sure that the correct bit compiler is 114 111 being sourced in windows/configs (e.g. sdk7.1.win7-64.sh or sdk7.1.win7-32.sh) see 115 112 section "One note about 32 vs 64 bit compile" below. 116 117 118 119 113 120 114 Once the cl.exe compiler works, you can start installing the following packages: … … 125 119 For cccl, use install-win7.sh 126 120 For triangle, use install-win7.sh 121 122 Once this is complete run the install.sh scripts in the autoconf and automake 123 externalpackages directory 127 124 128 125 Once these externalpackages have been compiled, you can compile issm: … … 137 134 138 135 139 140 141 136 One note about 32 vs 64 bit compile: 142 depending on your Matlab version, you will need to do a 32 or 64 bit compile. The only 143 difference between both compiles is the setup of the cl.exe compiler. For ease of use, 144 you will find in externalpackages/windows/windows_environment.sh a switch to go from 32 145 to 64 bit compile. When you type cl.exe \help at the command prompt, cl.exe should report 146 what system it is compiling for. 147 Beware, switching 32 to 64 or vice-versa implies recompiling everything from scratch. 148 149 150 137 Depending on your Matlab version, you will need to do a 32 or 64 bit compile. The only 138 difference between both compiles is the setup of the cl.exe compiler. For ease of use, 139 you will find in externalpackages/windows/windows_environment.sh a switch to go from 32 140 to 64 bit compile. When you type cl.exe \help at the command prompt, cl.exe should report 141 what system it is compiling for. Beware, switching 32 to 64 or vice-versa implies recompiling everything from scratch. 151 142 152 143 153 144 154 145 How to setup a Cron job? 155 Rownlaod exim and cron from cygwin. Run exim-config (don't forget to launch your cygwin terminal as 146 Download exim and cron from cygwin setup. Run exim-config (don't forget to launch your cygwin terminal as 156 147 Administrator). If asked for a daemon name, type ntsec. Also, if cron complains about sendmail, 157 symlink /usr/lib/sendmail to /usr/sbin/sendmail. Then link /usr/sbin/sendmail to /usr/bin/exim. 158 Alternatively, if you have an smtp server, you can download and configure ssmtp. Run ssmtp-config 148 symlink /usr/lib/sendmail to /usr/sbin/sendmail. Then link /usr/sbin/sendmail 149 to /usr/bin/exim. Alternatively, if you have an smtp server, you can download and configure 150 ssmtp. Run ssmtp-config 159 151 as Administrator and link /usr/sbin/sendmail to /usr/bin/ssmtp. After the email has been configured, 160 run cron-config as Administrator. 152 run cron-config as Administrator.
Note:
See TracChangeset
for help on using the changeset viewer.