Download PVF User's Guide

Macro Name
Description
$(SolutionName)
The base name of the solution.
$(SolutionFileName)
The file name of the solution file.
$(SolutionExt)
The file extension of the solution file, including the ‘.’
before the file extension.
$(TargetDir)
The directory of the primary output file of the build.
$(TargetPath)
The full path name of the primary output file of the build.
$(TargetFileName)
The file name of the primary output file of the build.
$(TargetExt)
The file extension of the primary output file of the build,
including the ‘.’ before the file extension.
$(VSInstallDir)
The Visual Studio 2005 installation directory.
$(VCInstallDir)
The Visual C++ 2005 installation directory. If Visual C++
2005 is not installed, this macro may evaluate to a directory
that does not exist.
$(OpenToolsDir) [PGI only]
The location of the Open Tools installation directory,
including files needed for building Microsoft Windows
applications for both 32-bit and 64-bit environments.
$(PGITools32Dir) [PGI only]
The location of the active PGI toolset for 32-bit targets. This
directory is the parent of bin, lib, and include directories
containing executables, libraries, and include files for the
PGI development environment.
$(PGIToolsDir) [PGI only]
The location of the active PGI toolset for 64-bit targets. This
directory is the parent of bin, lib, and include directories
containing executables, libraries, and include files for the
PGI development environment.
1.11
Debugging with PVF
PVF utilizes the Visual Studio debugger for debugging Fortran programs. PGI has implemented a
custom debug engine that provides the language-specific debugging capability required for Fortran.
This debug engine also supports Visual C++.
The Debug configuration is usually used for debugging. By default, this configuration will build the
application so that debugging information is provided.
8
Getting Started with PVF