Skip to main content

more options


Porting a Package

Given the source code and a set of makefiles for a package, you have three options for porting it to the Windows 2000/XP environment of the Velocity Complex:

  • You can leave the makefile intact and try to run it under Cygwin/MinGW.
  • You can modify the makefile to make it acceptable to Nmake.
  • You can create a VS .NET Solution containing projects for each library and executable in the package.

Portability Libraries

The Intel Fortran compiler provides portability functions (/4Yportlib). See Table 1-1 in the Intel Fortran Libraries Reference.

For C/C++ programs see the sections on Porting from UNIX to Win32 in the Microsoft Help.

Given the source code and a set of makefiles for a package, you have three options for porting it to the Windows 2000/XP environment of the Velocity Complex:

  • You can leave the makefile intact and try to run it under Cygwin/MinGW.
  • You can modify the makefile to make it acceptable to Nmake.
  • You can create a VS .NET Solution containing projects for each library and executable in the package.

Regardless of which of the above you choose, you will need to make adjustments to the source code to replace OS-specific routines with similar utilities provided by Windows. The symbol _WIN32 is automatically defined by each compiler and it can be used with #ifdef directives for conditional compilation of code, using the C or Fortran preprocessors as appropriate. (The C preprocessor is automatically invoked for C programs.)

Portability Libraries

The Intel Fortran compiler provides portability functions (/4Yportlib). See Table 1-1 in the Intel Fortran Libraries Reference.

For C/C++ programs see the sections on Porting from UNIX to Win32 in the Microsoft Help.