%scons; %builders-mod; %functions-mod; %tools-mod; %variables-mod; ]>

Sets construction variables for the Microsoft linker.

SHLINK SHLINKFLAGS SHLINKCOM LINK LINKFLAGS LINKCOM LIBDIRPREFIX LIBDIRSUFFIX LIBLINKPREFIX LIBLINKSUFFIX WINDOWSDEFPREFIX WINDOWSDEFSUFFIX WINDOWS_INSERT_DEF WINDOWSEXPPREFIX WINDOWSEXPSUFFIX WINDOWSSHLIBMANIFESTPREFIX WINDOWSSHLIBMANIFESTSUFFIX WINDOWSPROGMANIFESTPREFIX WINDOWSPROGMANIFESTSUFFIX REGSVR REGSVRFLAGS REGSVRCOM LDMODULE LDMODULEPREFIX LDMODULESUFFIX LDMODULEFLAGS LDMODULECOM SHLINKCOMSTR LINKCOMSTR REGSVRCOMSTR LDMODULECOMSTR

When set to non-zero, suppresses creation of a corresponding Windows static import lib by the &b-link-SharedLibrary; builder when used with MinGW, Microsoft Visual Studio or Metrowerks. This also suppresses creation of an export (.exp) file when using Microsoft Visual Studio.

The Microsoft Visual C++ PDB file that will store debugging information for object files, shared libraries, and programs. This variable is ignored by tools other than Microsoft Visual C++. When this variable is defined SCons will add options to the compiler and linker command line to cause them to generate external debugging information, and will also set up the dependencies for the PDB file. Example: env['PDB'] = 'hello.pdb' The Visual C++ compiler switch that SCons uses by default to generate PDB information is /Z7. This works correctly with parallel (-j) builds because it embeds the debug information in the intermediate object files, as opposed to sharing a single PDB file between multiple object files. This is also the only way to get debug information embedded into a static library. Using the /Zi instead may yield improved link-time performance, although parallel builds will no longer work. You can generate PDB files with the /Zi switch by overriding the default &cv-link-CCPDBFLAGS; variable; see the entry for that variable for specific examples.

Set to True to embed the compiler-generated manifest (normally ${TARGET}.manifest) into all Windows executables and DLLs built with this environment, as a resource during their link step. This is done using &cv-link-MT; and &cv-link-MTEXECOM; and &cv-link-MTSHLIBCOM;. See also &cv-link-WINDOWS_INSERT_MANIFEST;.

The program used on Windows systems to embed manifests into DLLs and EXEs. See also &cv-link-WINDOWS_EMBED_MANIFEST;.

Flags passed to the &cv-link-MT; manifest embedding program (Windows only).

The Windows command line used to embed manifests into executables. See also &cv-link-MTSHLIBCOM;.

The Windows command line used to embed manifests into shared libraries (DLLs). See also &cv-link-MTEXECOM;.

The program used on Windows systems to register a newly-built DLL library whenever the &b-link-SharedLibrary; builder is passed a keyword argument of register=True.

The command line used on Windows systems to register a newly-built DLL library whenever the &b-link-SharedLibrary; builder is passed a keyword argument of register=True.

The string displayed when registering a newly-built DLL file. If this is not set, then &cv-link-REGSVRCOM; (the command line) is displayed.

Flags passed to the DLL registration program on Windows systems when a newly-built DLL library is registered. By default, this includes the /s that prevents dialog boxes from popping up and requiring user attention.

If set to true, a library build of a Windows shared library (.dll file) will include a reference to the corresponding module-definition file at the same time, if a module-definition file is not already listed as a build target. The name of the module-definition file will be constructed from the base name of the library and the &consvars; &cv-link-WINDOWSDEFSUFFIX; and &cv-link-WINDOWSDEFPREFIX;. The default is to not add a module-definition file. The module-definition file is not created by this directive, and must be supplied by the developer.

If set to true, &scons; will add the manifest file generated by Microsoft Visual C++ 8.0 and later to the target list so &SCons; will be aware they were generated. In the case of an executable, the manifest file name is constructed using &cv-link-WINDOWSPROGMANIFESTSUFFIX; and &cv-link-WINDOWSPROGMANIFESTPREFIX;. In the case of a shared library, the manifest file name is constructed using &cv-link-WINDOWSSHLIBMANIFESTSUFFIX; and &cv-link-WINDOWSSHLIBMANIFESTPREFIX;. See also &cv-link-WINDOWS_EMBED_MANIFEST;.

The prefix used for a Windows linker module-definition file name. Defaults to empty.

The suffix used for a Windows linker module-definition file name. Defaults to .def.

The prefix used for Windows linker exports file names. Defaults to empty.

The suffix used for Windows linker exports file names. Defaults to .exp.

The prefix used for executable program manifest files generated by Microsoft Visual C/C++. Defaults to empty.

The suffix used for executable program manifest files generated by Microsoft Visual C/C++. Defaults to .manifest.

The prefix used for shared library manifest files generated by Microsoft Visual C/C++. Defaults to empty.

The suffix used for shared library manifest files generated by Microsoft Visual C/C++. Defaults to .manifest.