# Microsoft Visual C++
# (C) Copyright David Abrahams 2001.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt)
# The following #// line will be used by the regression test table generation
# program as the column heading for HTML tables. Must not include version number.
#//Micro-
soft
VC++
# singleton variables...
set-as-singleton MSVCDir VISUALC MSVC_ROOT VC_TOOL_PATH VC_SETUP ;
# Get these variable set on the targets so that we can re-use the
# build actions for other toolsets using this one as a base.
flags msvc VC_TOOL_PATH ;
flags msvc VC_SETUP ;
flags msvc VC_COMPILER ;
flags msvc VC_LINKER ;
flags msvc VC_PDB_NAME ;
# compute MSVC tool path
# You can either put the msvc bin directory in your PATH, or you can set
# MSVCDir to point at the msvc installation directory
# Some installations set MSVCDIR instead of MSVCDir; who knows why?
MSVCDir ?= $(MSVCDIR) ;
# If MSVCDir is not set the user hasn't run VCVARS32.BAT
if ! $(MSVCDir)
{
# In case someone set VISUALC in order to build Jam, we can just use that.
MSVC_ROOT ?= $(VISUALC) ;
# Otherwise, guess a standard installation directory
ProgramFiles ?= $(PROGRAMFILES) ;
MSVC_ROOT ?= $(ProgramFiles:J=" ")"\\Microsoft Visual Studio\\VC98" ;
# Reconstitutes paths containing spaces
MSVC_ROOT = $(MSVC_ROOT:J=" ") ;
# The tools are provisionallly located in the msvc6 bin
# directory. This may be overridden by toolsets which extend this
# one.
VC_TOOL_PATH = "$(MSVC_ROOT)"$(SLASH)bin$(SLASH) ;
# Always call VCVARS32.BAT before invoking the tools
VC_SETUP = "CALL \"$(VC_TOOL_PATH)VCVARS32.BAT\" >nul" ;
}
else
{
# Reconstitutes paths containing spaces
MSVCDir = $(MSVCDir:J=" ") ;
# Don't clobber adjoining text or use explicit paths if MSVCDir is already set
VC_TOOL_PATH = "" ;
}
VC_COMPILER = cl ;
VC_LINKER = link ;
VC_PDB_NAME = vc60 ;
VC_STDLIB_PATH = ;
flags msvc CFLAGS on/object : /Z7 ;
flags msvc CFLAGS on/database : /Zi ;
flags msvc PDB_CFLAG on/database : /Fd ;
flags msvc PDB_LINKFLAG on/database : /PDB: ;
flags msvc LINKFLAGS on : /DEBUG ;
# The linker disables the default optimizations when using /DEBUG. Whe have
# to enable them manually for release builds with debug symbols.
flags msvc LINKFLAGS on/release : /OPT:REF,ICF ;
flags msvc CFLAGS off : /Od ;
flags msvc CFLAGS speed : /Ogity /O2 /Gs ;
flags msvc CFLAGS space : /Ogisy /O1 /Gs ;
flags msvc CFLAGS off : /Ob0 ;
flags msvc CFLAGS on : /Ob1 ;
flags msvc CFLAGS full : /Ob2 ;
flags msvc CFLAGS on : /EHsc ;
flags msvc CFLAGS on : /GR ;
# Note that these two options actually imply multithreading support on MSVC
# because there is no single-threaded dynamic runtime library. Specifying
# multi would be a bad idea, though, because no option would be
# matched when the build uses the default settings of dynamic
# and single.
flags msvc CFLAGS release/dynamic : /MD ;
flags msvc CFLAGS debug/dynamic : /MDd ;
flags msvc CFLAGS release/static/single : /ML ;
flags msvc CFLAGS debug/static/single : /MLd ;
flags msvc CFLAGS release/static/multi : /MT ;
flags msvc CFLAGS debug/static/multi : /MTd ;
flags msvc CFLAGS ;
flags msvc C++FLAGS ;
flags msvc DEFINES ;
flags msvc UNDEFS ;
flags msvc HDRS ;
flags msvc SYSHDRS ;
flags msvc LINKFLAGS ;
flags msvc ARFLAGS ;
flags msvc STDHDRS : $(MSVCDir)$(SLASH)include ;
flags msvc STDLIBPATH : $(MSVCDir)$(SLASH)lib ;
flags msvc LIBPATH ;
flags msvc NEEDLIBS ;
flags msvc FINDLIBS ;
flags msvc LINKFLAGS $(SHARED_TYPES) : /DLL ;
flags msvc LINKFLAGS console : /subsystem:console ;
flags msvc LINKFLAGS gui : /subsystem:windows ;
flags msvc LINKFLAGS wince : /subsystem:windowsce ;
flags msvc LINKFLAGS native : /subsystem:native ;
flags msvc LINKFLAGS auto : /subsystem:posix ;
rule vc-set-pdb-file ( targets + : name )
{
local pdb = $(targets[1]:B=$(name):S=.pdb) ;
VC_PDB_FILE on $(targets) = $(pdb:G=:R=$(LOCATE_TARGET)) ;
LOCATE on $(pdb) = $(LOCATE_TARGET) ;
Clean clean : $(pdb) ;
}
#### Link ####
rule Link-action ( target implib ? : sources + : target-type ? )
{
with-command-file vc-Link $(<) : $(sources) $(NEEDLIBS) ;
if $(target-type) in $(SHARED_TYPES)
{
MANIFEST on $(target) = $(VC_MANIFEST) ;
OUTPUTRESOURCE on $(target) = $(VC_OUTPUTRESOURCE) ;
}
gRUN_PATH($(<)) += $(VC_STDLIB_PATH) ;
if $(implib)
{
# incremental linking a DLL causes no end of problems: if the
# actual exports don't change, the import .lib file is never
# updated. Therefore, the .lib is always out-of-date and gets
# rebuilt every time. I'm not sure that incremental linking is
# such a great idea in general, but in this case I'm sure we
# don't want it.
NOINCREMENTAL on $(<) = /INCREMENTAL:NO ;
}
vc-set-pdb-file $(<) : $(target:B) ;
}
VC_MANIFEST = ;
VC_OUTPUTRESOURCE = ;
actions together vc-Link
{
$(VC_SETUP)
"$(VC_TOOL_PATH)$(VC_LINKER)" /nologo $(NOINCREMENTAL) $(LINKFLAGS) $(PDB_LINKFLAG)"$(VC_PDB_FILE)" /out:"$(<[1])" /IMPLIB:"$(<[2])" /LIBPATH:"$(LIBPATH)" /LIBPATH:"$(STDLIBPATH)" "$(FINDLIBS:S=.lib)" @"$(>)"
$(MANIFEST)$(<[1]).manifest $(OUTPUTRESOURCE)$(<[1]);#2
}
#### Cc #####
rule Cc-action
{
vc-set-pdb-file $(<) : $(VC_PDB_NAME) ;
vc-Cc $(<) : $(>) ;
}
actions vc-Cc
{
$(VC_SETUP)
"$(VC_TOOL_PATH)$(VC_COMPILER)" /Zm800 -nologo -c -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) -I"$(HDRS)" -I"$(STDHDRS)" -I"$(SYSHDRS)" $(PDB_CFLAG)"$(VC_PDB_FILE)" -Fo"$(<)" "$(>)"
}
#### C++ ####
rule C++-action
{
vc-set-pdb-file $(<) : $(VC_PDB_NAME) ;
vc-C++ $(<) : $(>) ;
}
actions vc-C++
{
$(VC_SETUP)
"$(VC_TOOL_PATH)$(VC_COMPILER)" /Zm800 -nologo /EHsc -c -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) $(C++FLAGS) -I"$(HDRS)" -I"$(STDHDRS)" -I"$(SYSHDRS)" $(PDB_CFLAG)"$(VC_PDB_FILE)" -Fo"$(<)" -Tp"$(>)"
}
#### Archive ####
rule Archive-action
{
vc-set-pdb-file $(<) : $(<:B) ;
with-command-file vc-Archive $(<) : $(>) ;
}
actions vc-Archive
{
$(VC_SETUP)
if exist "$(<)" DEL "$(<)"
"$(VC_TOOL_PATH)$(VC_LINKER)" /lib $(ARFLAGS) $(PDB_LINKFLAG)"$(VC_PDB_FILE)" /out:"$(<)" @"$(>)"
}