Index: /issm/trunk-jpl/externalpackages/petsc/install-3.5-win7.sh
===================================================================
--- /issm/trunk-jpl/externalpackages/petsc/install-3.5-win7.sh	(revision 19541)
+++ /issm/trunk-jpl/externalpackages/petsc/install-3.5-win7.sh	(revision 19542)
@@ -7,5 +7,5 @@
 
 #Download from ISSM server
-$ISSM_DIR/scripts/DownloadExternalPackage.py 'http://issm.jpl.nasa.gov/files/externalpackages/petsc-lite-3.5.3.tar.gz' 'petsc-3.5.3.tar.gz'
+#$ISSM_DIR/scripts/DownloadExternalPackage.py 'http://issm.jpl.nasa.gov/files/externalpackages/petsc-lite-3.5.3.tar.gz' 'petsc-3.5.3.tar.gz'
 
 #Untar and move petsc to install directory
Index: /issm/trunk-jpl/externalpackages/windows/configs/sdk10.0-win64.sh
===================================================================
--- /issm/trunk-jpl/externalpackages/windows/configs/sdk10.0-win64.sh	(revision 19542)
+++ /issm/trunk-jpl/externalpackages/windows/configs/sdk10.0-win64.sh	(revision 19542)
@@ -0,0 +1,48 @@
+
+# -----------------------------------------------------------------------------
+# 
+# The following variables can vary from system to system and standard
+# installation is assumed throughout. If different directories were used when
+# installing MSVC, or Win SDK.
+#
+# TODO: Bring out the host machine arhictecture specific stuff from INCLUDE,
+# LIB and LIBPATH.
+#
+# -----------------------------------------------------------------------------
+
+# The version of Visual Studio is 10.0. Newer versions should work as well.
+export MSVC_DIR='C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\'
+
+# SDK change from 7 to 8 involved changing the locations of important 
+# libraries. If you wish to use 8.0 or 8.1 then you need to provide the 
+# directory of 'Windows Kits' instead.
+export MPI_DIR='C:\Programs\MPICH2'
+
+# Unfotunately, standard installation directories of Matlab usually include 
+# white spaces that are not handled correctly by the command interpreter. As
+# such, the directory where one would find Matlab headers and libraries might
+# need to be provided as environment variables.
+export MATLAB_DIR_WIN=`cygpath -w ${MATLAB_DIR}`
+export MATLAB_DIR_LIB="${MATLAB_DIR_WIN}\\extern\\lib\\win64\\microsoft"
+
+# Information about the .NET framework is required to run the MSVC toolchain
+export FrameworkDir='C:\Windows\Microsoft.NET\Framework64\'
+export FrameworkVersion=v4.0.30319
+
+# Windows Kit Information
+export WIN_KIT_DIR='C:\Program Files (x86)\Windows Kits\10'
+export WIN_KIT_VER='10.0.10240.0'
+export WIN_KIT_INC="${WIN_KIT_DIR}\\Include\\${WIN_KIT_VER}\\ucrt;${WIN_KIT_DIR}\\Include\\${WIN_KIT_VER}\\um;${WIN_KIT_DIR}\\Include\\${WIN_KIT_VER}\\shared"
+export WIN_KIT_LIB="${WIN_KIT_DIR}\\Lib\\${WIN_KIT_VER}\\um\\x64;${WIN_KIT_DIR}\\Lib\\${WIN_KIT_VER}\\ucrt\\x64"
+
+
+# LIB and LIBPATH seem redundant, but MSVC linker and compiler use different 
+# variables for the same purpose.
+export INCLUDE="${MSVC_DIR}include;${MATLAB_DIR_WIN}\\extern\\include;${WIN_KIT_INC};"
+export LIB="${MSVC_DIR}lib\\amd64;${MATLAB_DIR_LIB};${WIN_KIT_LIB};"
+export LIBPATH="${FrameworkDir}${FrameworkVersion};${MATLAB_DIR_LIB};${WIN_KIT_LIB};"
+export LIBPATH="${LIBPATH}${MSVC_DIR}lib\\amd64;${MSVC_DIR}bin\\amd64;"
+
+export MSVC_DIR_UNIX=`cygpath -u "${MSVC_DIR}"`
+export MPI_DIR_UNIX=`cygpath -u "${MPI_DIR}"`
+export PATH="${MSVC_DIR_UNIX}/bin/amd64:${MPI_DIR_UNIX}/bin:$PATH"
