/usr/share/boost-build/src/tools
Edit: /usr/share/boost-build/src/tools/clang-darwin.jam (6713B)
# Copyright Vladimir Prus 2004.
# Copyright Noel Belcourt 2007.
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt
# or copy at http://www.boost.org/LICENSE_1_0.txt)
import clang ;
import feature : feature ;
import os ;
import toolset ;
import toolset : flags ;
import gcc ;
import common ;
import errors ;
import generators ;
feature.extend-subfeature toolset clang : platform : darwin ;
toolset.inherit-generators clang-darwin
clang darwin
: gcc
# Don't inherit PCH generators. They were not tested, and probably
# don't work for this compiler.
: gcc.mingw.link gcc.mingw.link.dll gcc.compile.c.pch gcc.compile.c++.pch
;
generators.override clang-darwin.prebuilt : builtin.lib-generator ;
generators.override clang-darwin.prebuilt : builtin.prebuilt ;
generators.override clang-darwin.searched-lib-generator : searched-lib-generator ;
generators.register-c-compiler clang-darwin.compile.m : OBJECTIVE_C : OBJ : clang darwin ;
generators.register-c-compiler clang-darwin.compile.mm : OBJECTIVE_CPP : OBJ : clang darwin ;
toolset.inherit-rules clang-darwin : gcc ;
toolset.inherit-flags clang-darwin : gcc
: full
x86/32
x86/64
on/full
on/fat
;
if [ MATCH (--debug-configuration) : [ modules.peek : ARGV ] ]
{
.debug-configuration = true ;
}
# Initializes the clang-darwin toolset
# version in optional
# name (default clang++) is used to invoke the specified clang compiler
# compile and link options allow you to specify addition command line options for each version
rule init ( version ? : command * : options * )
{
command = [ common.get-invocation-command clang-darwin : clang++
: $(command) : /usr/bin /usr/local/bin ] ;
# Determine the version
local command-string = $(command:J=" ") ;
if $(command)
{
version ?= [ MATCH "version ([0-9]+[.][0-9]+)"
: [ SHELL "$(command-string) --version" ] ] ;
}
local condition = [ common.check-init-parameters clang
: version $(version) ] ;
common.handle-options clang-darwin : $(condition) : $(command) : $(options) ;
clang.init-cxxstd-flags clang-darwin : $(condition) : $(version) ;
# - Ranlib.
local ranlib = [ feature.get-values : $(options) ] ;
toolset.flags clang-darwin.archive .RANLIB $(condition) : $(ranlib[1]) ;
# - Archive builder.
local archiver = [ feature.get-values : $(options) ] ;
toolset.flags clang-darwin.archive .AR $(condition) : $(archiver[1]) ;
}
SPACE = " " ;
toolset.flags clang-darwin.compile.m OPTIONS ;
toolset.flags clang-darwin.compile.mm OPTIONS ;
toolset.flags clang-darwin.compile.mm OPTIONS ;
# Declare flags and action for compilation.
# For clang, 'on' and 'full' are identical
toolset.flags clang-darwin.compile OPTIONS full : -Wno-inline ;
# SJW 12/2017: Support for is widely inconsistent.
# shouldn't this be handled by the common gcc?
toolset.flags clang-darwin.compile OPTIONS ;
# LTO
toolset.flags clang-darwin.compile OPTIONS on/thin : -flto=thin ;
toolset.flags clang-darwin.link OPTIONS on/thin : -flto=thin ;
toolset.flags clang-darwin.compile OPTIONS on/full : -flto=full ;
toolset.flags clang-darwin.link OPTIONS on/full : -flto=full ;
# stdlib selection
toolset.flags clang-darwin.compile OPTIONS gnu gnu11 : -stdlib=libstdc++ ;
toolset.flags clang-darwin.link OPTIONS gnu gnu11 : -stdlib=libstdc++ ;
toolset.flags clang-darwin.compile OPTIONS libc++ : -stdlib=libc++ ;
toolset.flags clang-darwin.link OPTIONS libc++ : -stdlib=libc++ ;
actions compile.c
{
"$(CONFIG_COMMAND)" -x c $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES) -I"$(INCLUDES)" -c -o "$(<)" "$(>)"
}
actions compile.c++
{
"$(CONFIG_COMMAND)" -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES) -I"$(INCLUDES)" -c -o "$(<)" "$(>)"
}
actions compile.m
{
"$(CONFIG_COMMAND)" -x objective-c $(OPTIONS) -D$(DEFINES) -I"$(INCLUDES)" -c -o "$(<)" "$(>)"
}
actions compile.mm
{
"$(CONFIG_COMMAND)" -x objective-c++ $(OPTIONS) -D$(DEFINES) -I"$(INCLUDES)" -c -o "$(<)" "$(>)"
}
# Default value. Mostly for the sake of clang-linux
# that inherits from gcc, but does not has the same
# logic to set the .AR variable. We can put the same
# logic in clang-linux, but that's hardly worth the trouble
# as on Linux, 'ar' is always available.
.AR = ar ;
.RANLIB = ranlib -cs ;
rule archive ( targets * : sources * : properties * )
{
# Always remove archive and start again. Here's rationale from
# Andre Hentz:
#
# I had a file, say a1.c, that was included into liba.a.
# I moved a1.c to a2.c, updated my Jamfiles and rebuilt.
# My program was crashing with absurd errors.
# After some debugging I traced it back to the fact that a1.o was *still*
# in liba.a
#
# Rene Rivera:
#
# Originally removing the archive was done by splicing an RM
# onto the archive action. That makes archives fail to build on NT
# when they have many files because it will no longer execute the
# action directly and blow the line length limit. Instead we
# remove the file in a different action, just before the building
# of the archive.
#
local clean.a = $(targets[1])(clean) ;
TEMPORARY $(clean.a) ;
NOCARE $(clean.a) ;
LOCATE on $(clean.a) = [ on $(targets[1]) return $(LOCATE) ] ;
DEPENDS $(clean.a) : $(sources) ;
DEPENDS $(targets) : $(clean.a) ;
common.RmTemps $(clean.a) : $(targets) ;
}
actions piecemeal archive
{
"$(.AR)" $(AROPTIONS) rc "$(<)" "$(>)"
"$(.RANLIB)" "$(<)"
}
# Declare actions for linking
rule link ( targets * : sources * : properties * )
{
SPACE on $(targets) = " " ;
# Serialize execution of the 'link' action, since
# running N links in parallel is just slower.
JAM_SEMAPHORE on $(targets) = clang-darwin-link-semaphore ;
}
actions link bind LIBRARIES
{
"$(CONFIG_COMMAND)" $(USER_OPTIONS) -L"$(LINKPATH)" -o "$(<)" "$(>)" "$(LIBRARIES)" $(START-GROUP) $(FINDLIBS-ST-PFX) -l$(FINDLIBS-ST) $(FINDLIBS-SA-PFX) -l$(FINDLIBS-SA) $(END-GROUP) $(OPTIONS)
}
actions link.dll bind LIBRARIES
{
"$(CONFIG_COMMAND)" $(USER_OPTIONS) -L"$(LINKPATH)" -o "$(<)" -single_module -dynamiclib -install_name "@rpath/$(<[1]:D=)" "$(>)" "$(LIBRARIES)" $(START-GROUP) $(FINDLIBS-ST-PFX) -l$(FINDLIBS-ST) $(FINDLIBS-SA-PFX) -l$(FINDLIBS-SA) $(END-GROUP) $(OPTIONS)
}