Index: /issm/trunk-jpl/externalpackages/windows/InstallInstructions.txt =================================================================== --- /issm/trunk-jpl/externalpackages/windows/InstallInstructions.txt (revision 11945) +++ /issm/trunk-jpl/externalpackages/windows/InstallInstructions.txt (revision 11946) @@ -19,6 +19,6 @@ Cygwin: --You will need cygwin installed on your Windows platform to manage the compilation. -The compilation will still be carried out by the windows sdk compiler, but the +-You will need cygwin installed on your Windows platform to manage the compilation. Cygwin emulates +unix behaviour on windows machines. The compilation will still be carried out by the windows sdk compiler, but the environment driving the compilation will be the unix-like cygwin. When you download cygwin, make sure that you install it in the C:\Cygwin directory. @@ -62,5 +62,5 @@ This is by far the most tricky part. -Follow Figure 2 for more details. You have to launch sdk 7.1 command prompt, go to the +Follow Sdk1.png and Sdk2.png for more details. You have to launch sdk 7.1 command prompt, go to the cygwin directory and fire up Cygwin by executing Cygwin.bat. Once this is done,dump the results of the export command onto a file, called sdk7.1.win7.64.sh @@ -71,5 +71,5 @@ Downloading issm: -Download issm onto the C:\ directory. Do not download it in your Documents or Desktop +Download issm into the C:\ directory. Do not download it in your Documents or Desktop folder. @@ -103,18 +103,12 @@ cl hello.cpp -If this does not work, do not go any further! The settings of your cl compiler are found -in externalpackages/windows/configs/ -First, you can try updating the user-specific settings to refer to your username and then -trying to run cl hello.cpp again. -If there is still a significant different between your 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 -the configs directory. Relaunch bash, and try to run cl hello.cpp once more. Beware, you will likely -have to erase some lines in your file, as cygwin might not like some of the stuff that your +If this does not work, do not go any further! The settings of your cl compiler are found +in externalpackages/windows/configs/. If there is a significant different between your +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 +the configs directory. Relaunch bash, and try to run cl hello.cpp once more. Beware, you will likely +have to erase some lines in your file, as cygwin might not like some of the stuff that your Windows platform is trying to define. To make sure that the correct bit compiler is being sourced in windows/configs (e.g. sdk7.1.win7-64.sh or sdk7.1.win7-32.sh) see section "One note about 32 vs 64 bit compile" below. - - - Once the cl.exe compiler works, you can start installing the following packages: @@ -125,4 +119,7 @@ For cccl, use install-win7.sh For triangle, use install-win7.sh + +Once this is complete run the install.sh scripts in the autoconf and automake +externalpackages directory Once these externalpackages have been compiled, you can compile issm: @@ -137,24 +134,19 @@ - - One note about 32 vs 64 bit compile: -depending on your Matlab version, you will need to do a 32 or 64 bit compile. The only -difference between both compiles is the setup of the cl.exe compiler. For ease of use, -you will find in externalpackages/windows/windows_environment.sh a switch to go from 32 -to 64 bit compile. When you type cl.exe \help at the command prompt, cl.exe should report -what system it is compiling for. -Beware, switching 32 to 64 or vice-versa implies recompiling everything from scratch. - - - +Depending on your Matlab version, you will need to do a 32 or 64 bit compile. The only +difference between both compiles is the setup of the cl.exe compiler. For ease of use, +you will find in externalpackages/windows/windows_environment.sh a switch to go from 32 +to 64 bit compile. When you type cl.exe \help at the command prompt, cl.exe should report +what system it is compiling for. Beware, switching 32 to 64 or vice-versa implies recompiling everything from scratch. How to setup a Cron job? -Rownlaod exim and cron from cygwin. Run exim-config (don't forget to launch your cygwin terminal as +Download exim and cron from cygwin setup. Run exim-config (don't forget to launch your cygwin terminal as Administrator). If asked for a daemon name, type ntsec. Also, if cron complains about sendmail, -symlink /usr/lib/sendmail to /usr/sbin/sendmail. Then link /usr/sbin/sendmail to /usr/bin/exim. -Alternatively, if you have an smtp server, you can download and configure ssmtp. Run ssmtp-config +symlink /usr/lib/sendmail to /usr/sbin/sendmail. Then link /usr/sbin/sendmail +to /usr/bin/exim. Alternatively, if you have an smtp server, you can download and configure +ssmtp. Run ssmtp-config as Administrator and link /usr/sbin/sendmail to /usr/bin/ssmtp. After the email has been configured, -run cron-config as Administrator. +run cron-config as Administrator.