... | @@ -51,7 +51,7 @@ Type and run `cl` command from appeared console, it should not complain that it |
... | @@ -51,7 +51,7 @@ Type and run `cl` command from appeared console, it should not complain that it |
|
Type `export PATH="/usr/bin:$PATH"` command in console. This will let you use Cygwin binaries. Notice that '/usr/bin' should go first, this will make Cygwin binaries prefferable over binaries with matching names.
|
|
Type `export PATH="/usr/bin:$PATH"` command in console. This will let you use Cygwin binaries. Notice that '/usr/bin' should go first, this will make Cygwin binaries prefferable over binaries with matching names.
|
|
|
|
|
|
|
|
|
|
To avoid conflict between link.exe executables in Cygwin and Visual Studio run command `mv /usr/bin/link.exe /usr/bin/link-cygwin.exe`. At the and we should not forget to return it back so that Cygwin will be still usable.
|
|
To avoid conflict between link.exe executables in Cygwin and Visual Studio run command `mv /usr/bin/link.exe /usr/bin/link-cygwin.exe`. At the end we should not forget to return it back so that Cygwin will be still usable.
|
|
|
|
|
|
|
|
|
|
Now switch to the petsc_source_dir directory. Type `bin/win32fe/win32fe.exe cl` it should return you some information on which flags can be passed to Visual Studio compiler. We just check that it works.
|
|
Now switch to the petsc_source_dir directory. Type `bin/win32fe/win32fe.exe cl` it should return you some information on which flags can be passed to Visual Studio compiler. We just check that it works.
|
... | | ... | |