1998-03-28 05:44:41 +03:00
#
2012-05-21 15:12:37 +04:00
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
1998-03-28 05:44:41 +03:00
#
# config.mk
#
# Determines the platform and builds the macros needed to load the
# appropriate platform-specific .mk file, then defines all (most?)
# of the generic macros.
#
2000-03-14 06:00:38 +03:00
# Define an include-at-most-once flag
2011-08-09 11:07:48 +04:00
i f d e f I N C L U D E D _ C O N F I G _ M K
2012-04-04 00:08:16 +04:00
$( error Do not include config .mk twice !)
2011-08-09 11:07:48 +04:00
e n d i f
2000-03-14 06:00:38 +03:00
INCLUDED_CONFIG_MK = 1
2005-07-23 00:11:37 +04:00
EXIT_ON_ERROR = set -e; # Shell loops continue past errors without this.
1998-08-20 00:42:14 +04:00
i f n d e f t o p s r c d i r
1998-09-05 05:10:54 +04:00
topsrcdir = $( DEPTH)
1998-08-20 00:42:14 +04:00
e n d i f
1998-03-28 05:44:41 +03:00
2000-03-14 06:00:38 +03:00
i f n d e f I N C L U D E D _ A U T O C O N F _ M K
1999-09-30 00:39:46 +04:00
i n c l u d e $( DEPTH ) / c o n f i g / a u t o c o n f . m k
1999-09-03 02:02:46 +04:00
e n d i f
2013-09-05 04:01:44 +04:00
- i n c l u d e $( DEPTH ) / . m o z c o n f i g . m k
2013-10-21 22:08:00 +04:00
i f n d e f E X T E R N A L L Y _ M A N A G E D _ M A K E _ F I L E
# Import the automatically generated backend file. If this file doesn't exist,
# the backend hasn't been properly configured. We want this to be a fatal
# error, hence not using "-include".
i f n d e f S T A N D A L O N E _ M A K E F I L E
GLOBAL_DEPS += backend.mk
i n c l u d e b a c k e n d . m k
e n d i f
e n d i f
2012-09-25 16:47:20 +04:00
space = $( NULL) $( NULL)
# Include defs.mk files that can be found in $(srcdir)/$(DEPTH),
# $(srcdir)/$(DEPTH-1), $(srcdir)/$(DEPTH-2), etc., and $(srcdir)
# where $(DEPTH-1) is one level less of depth, $(DEPTH-2), two, etc.
# i.e. for DEPTH=../../.., DEPTH-1 is ../.. and DEPTH-2 is ..
# These defs.mk files are used to define variables in a directory
# and all its subdirectories, recursively.
__depth := $( subst /, ,$( DEPTH) )
i f e q ( . , $( __depth ) )
__depth :=
e n d i f
$( foreach __d ,$ ( __depth ) .,$ ( eval __depth = $ ( wordlist 2,$ ( words $ ( __depth ) ) ,$ ( __depth ) ) $ ( eval -include $ ( subst $ ( space ) ,/,$ ( strip $ ( srcdir ) $ ( __depth ) defs .mk ) ) ) ) )
2008-06-06 23:31:11 +04:00
COMMA = ,
2007-03-26 22:15:02 +04:00
# Sanity check some variables
CHECK_VARS := \
XPI_NAME \
LIBRARY_NAME \
MODULE \
DEPTH \
XPI_PKGNAME \
INSTALL_EXTENSION_ID \
2008-12-24 22:04:43 +03:00
SHARED_LIBRARY_NAME \
2014-07-09 02:47:00 +04:00
SONAME \
2008-12-24 22:04:43 +03:00
STATIC_LIBRARY_NAME \
2007-03-26 22:15:02 +04:00
$( NULL)
# checks for internal spaces or trailing spaces in the variable
# named by $x
check-variable = $( if $( filter-out 0 1,$( words $( $( x) ) z) ) ,$( error Spaces are not allowed in $( x) ) )
$( foreach x ,$ ( CHECK_VARS ) ,$ ( check -variable ) )
2013-10-11 20:47:55 +04:00
i f n d e f I N C L U D E D _ F U N C T I O N S _ M K
2014-11-30 04:45:31 +03:00
i n c l u d e $( MOZILLA_DIR ) / c o n f i g / m a k e f i l e s / f u n c t i o n s . m k
2013-10-11 20:47:55 +04:00
e n d i f
2012-06-21 16:50:42 +04:00
RM = rm -f
2005-02-19 01:17:37 +03:00
# FINAL_TARGET specifies the location into which we copy end-user-shipped
2013-10-21 22:08:35 +04:00
# build products (typelibs, components, chrome). It may already be specified by
# a moz.build file.
2005-02-19 01:17:37 +03:00
#
2012-06-19 18:45:24 +04:00
# If XPI_NAME is set, the files will be shipped to $(DIST)/xpi-stage/$(XPI_NAME)
2012-12-11 19:37:07 +04:00
# instead of $(DIST)/bin. In both cases, if DIST_SUBDIR is set, the files will be
# shipped to a $(DIST_SUBDIR) subdirectory.
2013-10-21 22:08:35 +04:00
FINAL_TARGET ?= $( if $( XPI_NAME) ,$( DIST) /xpi-stage/$( XPI_NAME) ,$( DIST) /bin) $( DIST_SUBDIR:%= /%)
# Override the stored value for the check to make sure that the variable is not
# redefined in the Makefile.in value.
FINAL_TARGET_FROZEN := '$(FINAL_TARGET)'
2005-02-19 01:17:37 +03:00
2010-06-25 16:27:10 +04:00
i f d e f X P I _ N A M E
2015-10-30 05:31:14 +03:00
ACDEFINES += -DXPI_NAME= $( XPI_NAME)
2010-06-25 16:27:10 +04:00
e n d i f
2002-11-14 23:23:26 +03:00
# The VERSION_NUMBER is suffixed onto the end of the DLLs we ship.
VERSION_NUMBER = 50
2005-07-06 00:37:27 +04:00
i f e q ( $( HOST_OS_ARCH ) , W I N N T )
2014-11-30 04:45:31 +03:00
ifeq ( $( MOZILLA_DIR) ,$( topsrcdir) )
win_srcdir := $( subst $( topsrcdir) ,$( WIN_TOP_SRC) ,$( srcdir) )
else
# This means we're in comm-central's topsrcdir, so we need to adjust
# WIN_TOP_SRC (which points to mozilla's topsrcdir) for the substitution
# to win_srcdir.
cc_WIN_TOP_SRC := $( WIN_TOP_SRC:%/mozilla= %)
win_srcdir := $( subst $( topsrcdir) ,$( cc_WIN_TOP_SRC) ,$( srcdir) )
endif
BUILD_TOOLS = $( WIN_TOP_SRC) /build/unix
2005-06-02 08:00:37 +04:00
e l s e
2014-11-30 04:45:31 +03:00
win_srcdir := $( srcdir)
BUILD_TOOLS = $( MOZILLA_DIR) /build/unix
2005-06-02 08:00:37 +04:00
e n d i f
2004-03-23 11:41:30 +03:00
CONFIG_TOOLS = $( MOZ_BUILD_ROOT) /config
2014-11-30 04:45:31 +03:00
AUTOCONF_TOOLS = $( MOZILLA_DIR) /build/autoconf
2000-03-14 09:16:27 +03:00
2012-08-07 23:19:55 +04:00
i f d e f _ M S C _ V E R
2018-03-13 17:06:00 +03:00
# clang-cl is smart enough to generate dependencies directly.
i f n d e f C L A N G _ C L
2013-10-24 07:25:52 +04:00
CC_WRAPPER ?= $( call py_action,cl)
CXX_WRAPPER ?= $( call py_action,cl)
2018-03-13 17:06:00 +03:00
e n d i f # CLANG_CL
2012-08-07 23:19:55 +04:00
e n d i f # _MSC_VER
2010-08-05 03:59:23 +04:00
CC := $( CC_WRAPPER) $( CC)
CXX := $( CXX_WRAPPER) $( CXX)
2011-04-03 11:16:49 +04:00
MKDIR ?= mkdir
SLEEP ?= sleep
TOUCH ?= touch
2010-08-05 03:59:23 +04:00
2012-08-03 23:09:54 +04:00
PYTHON_PATH = $( PYTHON) $( topsrcdir) /config/pythonpath.py
2001-06-21 00:21:49 +04:00
#
2001-06-19 02:10:38 +04:00
# Build using PIC by default
#
_ENABLE_PIC = 1
2001-06-21 00:21:49 +04:00
2010-07-26 23:21:55 +04:00
# Don't build SIMPLE_PROGRAMS with PGO, since they don't need it anyway,
# and we don't have the same build logic to re-link them in the second pass.
i f d e f S I M P L E _ P R O G R A M S
NO_PROFILE_GUIDED_OPTIMIZE = 1
e n d i f
2011-04-14 13:23:13 +04:00
# No sense in profiling unit tests
i f d e f C P P _ U N I T _ T E S T S
NO_PROFILE_GUIDED_OPTIMIZE = 1
e n d i f
2008-02-17 01:23:07 +03:00
# Enable profile-based feedback
2013-11-02 03:42:53 +04:00
i f n e q ( 1 , $( NO_PROFILE_GUIDED_OPTIMIZE ) )
2004-03-21 05:31:17 +03:00
i f d e f M O Z _ P R O F I L E _ G E N E R A T E
2017-10-26 01:10:04 +03:00
PGO_CFLAGS += $( if $( filter $( notdir $<) ,$( notdir $( NO_PROFILE_GUIDED_OPTIMIZE) ) ) ,,$( PROFILE_GEN_CFLAGS) )
2017-11-02 21:47:48 +03:00
PGO_LDFLAGS += $( PROFILE_GEN_LDFLAGS)
2008-02-21 02:29:11 +03:00
i f e q ( W I N N T , $( OS_ARCH ) )
AR_FLAGS += -LTCG
e n d i f
e n d i f # MOZ_PROFILE_GENERATE
2008-02-17 01:23:07 +03:00
2004-03-21 05:31:17 +03:00
i f d e f M O Z _ P R O F I L E _ U S E
2017-10-26 01:10:04 +03:00
PGO_CFLAGS += $( if $( filter $( notdir $<) ,$( notdir $( NO_PROFILE_GUIDED_OPTIMIZE) ) ) ,,$( PROFILE_USE_CFLAGS) )
2017-11-02 21:47:48 +03:00
PGO_LDFLAGS += $( PROFILE_USE_LDFLAGS)
2008-02-21 02:29:11 +03:00
i f e q ( W I N N T , $( OS_ARCH ) )
AR_FLAGS += -LTCG
2004-03-21 05:31:17 +03:00
e n d i f
2008-02-21 02:29:11 +03:00
e n d i f # MOZ_PROFILE_USE
e n d i f # NO_PROFILE_GUIDED_OPTIMIZE
2004-03-21 05:31:17 +03:00
2017-12-11 20:02:49 +03:00
LOCALE_TOPDIR ?= $( topsrcdir)
2005-06-01 15:59:09 +04:00
MAKE_JARS_FLAGS = \
2017-12-11 20:02:49 +03:00
-t $( LOCALE_TOPDIR) \
2016-04-14 22:26:38 +03:00
-f $( MOZ_JAR_MAKER_FILE_FORMAT) \
2005-06-01 15:59:09 +04:00
$( NULL)
i f d e f U S E _ E X T E N S I O N _ M A N I F E S T
MAKE_JARS_FLAGS += -e
e n d i f
2013-07-10 13:55:01 +04:00
TAR_CREATE_FLAGS = -chf
2005-06-01 15:59:09 +04:00
1998-03-28 05:44:41 +03:00
#
# Default command macros; can be overridden in <arch>.mk.
#
2011-01-25 23:14:30 +03:00
CCC = $( CXX)
1998-03-28 05:44:41 +03:00
2009-05-18 22:15:05 +04:00
INCLUDES = \
-I$( srcdir) \
2015-12-30 07:46:38 +03:00
-I$( CURDIR) \
2013-11-19 23:10:15 +04:00
$( LOCAL_INCLUDES) \
2015-12-30 07:46:38 +03:00
-I$( ABS_DIST) /include \
2014-09-03 08:46:29 +04:00
$( NULL)
2014-11-30 04:45:31 +03:00
i n c l u d e $( MOZILLA_DIR ) / c o n f i g / s t a t i c - c h e c k i n g - c o n f i g . m k
2008-02-27 19:28:13 +03:00
2017-11-02 21:47:48 +03:00
LDFLAGS = $( COMPUTED_LDFLAGS) $( PGO_LDFLAGS) $( MK_LDFLAGS)
1999-02-10 02:24:12 +03:00
2017-10-27 20:38:10 +03:00
COMPILE_CFLAGS = $( COMPUTED_CFLAGS) $( PGO_CFLAGS) $( _DEPEND_CFLAGS) $( MK_COMPILE_DEFINES)
COMPILE_CXXFLAGS = $( COMPUTED_CXXFLAGS) $( PGO_CFLAGS) $( _DEPEND_CFLAGS) $( MK_COMPILE_DEFINES)
2015-05-08 08:04:15 +03:00
COMPILE_CMFLAGS = $( OS_COMPILE_CMFLAGS) $( MOZBUILD_CMFLAGS)
COMPILE_CMMFLAGS = $( OS_COMPILE_CMMFLAGS) $( MOZBUILD_CMMFLAGS)
2017-11-11 03:58:16 +03:00
ASFLAGS = $( COMPUTED_ASFLAGS)
2017-11-22 23:27:52 +03:00
SFLAGS = $( COMPUTED_SFLAGS)
2008-02-26 02:38:23 +03:00
2017-10-02 21:41:41 +03:00
HOST_CFLAGS = $( COMPUTED_HOST_CFLAGS) $( _DEPEND_CFLAGS)
HOST_CXXFLAGS = $( COMPUTED_HOST_CXXFLAGS) $( _DEPEND_CFLAGS)
2017-11-23 00:23:44 +03:00
HOST_C_LDFLAGS = $( COMPUTED_HOST_C_LDFLAGS)
HOST_CXX_LDFLAGS = $( COMPUTED_HOST_CXX_LDFLAGS)
2015-09-04 20:33:04 +03:00
2016-11-10 01:01:24 +03:00
# We only add color flags if neither the flag to disable color
# (e.g. "-fno-color-diagnostics" nor a flag to control color
# (e.g. "-fcolor-diagnostics=never") is present.
d e f i n e c o l o r i z e _ f l a g s
ifeq (,$(filter $(COLOR_CFLAGS : -f %=-fno -%), $$( 1) )$( findstring $ ( COLOR_CFLAGS ) ,$ $ ( 1) ) )
$(1) += $( COLOR_CFLAGS)
e n d i f
e n d e f
color_flags_vars := \
COMPILE_CFLAGS \
COMPILE_CXXFLAGS \
COMPILE_CMFLAGS \
COMPILE_CMMFLAGS \
LDFLAGS \
$( NULL)
i f d e f M A C H _ S T D O U T _ I S A T T Y
i f d e f C O L O R _ C F L A G S
2016-11-22 09:37:01 +03:00
# TODO Bug 1319166 - iTerm2 interprets some bytes sequences as a
# request to show a print dialog. Don't enable color on iTerm2 until
# a workaround is in place.
i f n e q ( $( TERM_PROGRAM ) , i T e r m . a p p )
2016-11-10 01:01:24 +03:00
$( foreach var ,$ ( color_flags_vars ) ,$ ( eval $ ( call colorize_flags ,$ ( var ) ) ) )
e n d i f
e n d i f
2016-11-22 09:37:01 +03:00
e n d i f
2016-11-10 01:01:24 +03:00
1998-03-28 05:44:41 +03:00
#
# Name of the binary code directories
#
1998-08-20 00:42:14 +04:00
# Override defaults
1998-08-27 23:52:22 +04:00
DEPENDENCIES = .md
1998-03-28 05:44:41 +03:00
2013-01-25 01:11:28 +04:00
i f d e f M A C O S X _ D E P L O Y M E N T _ T A R G E T
export MACOSX_DEPLOYMENT_TARGET
e n d i f # MACOSX_DEPLOYMENT_TARGET
2016-07-27 11:03:09 +03:00
# Export to propagate to cl and submake for third-party code.
# Eventually, we'll want to just use -I.
i f d e f I N C L U D E
export INCLUDE
e n d i f
2016-07-27 12:01:04 +03:00
# Export to propagate to link.exe and submake for third-party code.
# Eventually, we'll want to just use -LIBPATH.
i f d e f L I B
export LIB
e n d i f
2012-08-07 22:25:26 +04:00
i f d e f M O Z _ U S I N G _ C C A C H E
i f d e f C L A N G _ C X X
export CCACHE_CPP2 = 1
e n d i f
e n d i f
2005-04-22 23:06:27 +04:00
2002-09-05 10:28:15 +04:00
# Set link flags according to whether we want a console.
2014-08-27 13:20:10 +04:00
i f e q ( $( OS_ARCH ) , W I N N T )
2015-11-26 02:38:16 +03:00
i f d e f M O Z _ W I N C O N S O L E
2002-09-05 10:28:15 +04:00
i f e q ( $( MOZ_WINCONSOLE ) , 1 )
2015-11-26 02:38:16 +03:00
WIN32_EXE_LDFLAGS += $( WIN32_CONSOLE_EXE_LDFLAGS)
e l s e # MOZ_WINCONSOLE
WIN32_EXE_LDFLAGS += $( WIN32_GUI_EXE_LDFLAGS)
e n d i f
e l s e
# For setting subsystem version
2014-08-27 13:20:10 +04:00
WIN32_EXE_LDFLAGS += $( WIN32_CONSOLE_EXE_LDFLAGS)
2004-06-22 00:56:14 +04:00
e n d i f
2014-08-27 13:20:10 +04:00
e n d i f # WINNT
2002-09-05 10:28:15 +04:00
2013-02-14 10:22:00 +04:00
i f d e f _ M S C _ V E R
i f e q ( $( CPU_ARCH ) , x 8 6 _ 6 4 )
2017-09-28 12:31:47 +03:00
i f d e f M O Z _ A S A N
# ASan could have 3x stack memory usage of normal builds.
WIN32_EXE_LDFLAGS += -STACK:6291456
2017-03-20 05:52:00 +03:00
e l s e
2017-09-28 12:31:47 +03:00
# set stack to 2MB on x64 build. See bug 582910
WIN32_EXE_LDFLAGS += -STACK:2097152
e n d i f
2013-02-14 10:22:00 +04:00
e n d i f
2017-03-20 05:52:00 +03:00
e n d i f
2013-02-14 10:22:00 +04:00
2008-06-06 23:43:26 +04:00
- i n c l u d e $( topsrcdir ) / $( MOZ_BUILD_APP ) / a p p - c o n f i g . m k
1998-03-28 05:44:41 +03:00
######################################################################
2012-08-27 23:27:16 +04:00
GARBAGE += $( DEPENDENCIES) core $( wildcard core.[ 0-9] *) $( wildcard *.err) $( wildcard *.pure) $( wildcard *_pure_*.o) Templates.DB
1998-03-28 05:44:41 +03:00
2003-02-23 18:54:21 +03:00
i f e q ( $( OS_ARCH ) , D a r w i n )
i f n d e f N S D I S T M O D E
NSDISTMODE = absolute_symlink
e n d i f
2009-03-12 01:39:24 +03:00
PWD := $( CURDIR)
2003-02-23 18:54:21 +03:00
e n d i f
2014-11-30 04:45:31 +03:00
NSINSTALL_PY := $( PYTHON) $( abspath $( MOZILLA_DIR) /config/nsinstall.py)
2016-08-04 11:55:54 +03:00
i f n e q ( , $( or $ ( filter WINNT ,$ ( HOST_OS_ARCH ) ) ,$ ( if $ ( COMPILE_ENVIRONMENT ) ,,1) ) )
2012-07-03 10:43:06 +04:00
NSINSTALL = $( NSINSTALL_PY)
e l s e
2014-08-06 21:58:50 +04:00
NSINSTALL = $( DEPTH) /config/nsinstall$( HOST_BIN_SUFFIX)
2012-07-03 10:43:06 +04:00
e n d i f # WINNT
2005-07-28 23:48:12 +04:00
1998-03-28 05:44:41 +03:00
2014-02-11 02:57:01 +04:00
i f e q ( , $( CROSS_COMPILE ) $( filter -out WINNT , $ ( OS_ARCH ) ) )
2012-07-03 10:43:30 +04:00
INSTALL = $( NSINSTALL) -t
2005-07-28 23:48:12 +04:00
e l s e
2011-07-09 01:30:27 +04:00
# This isn't laid out as conditional directives so that NSDISTMODE can be
# target-specific.
2017-11-22 23:31:01 +03:00
INSTALL = $( if $( filter absolute_symlink, $( NSDISTMODE) ) , $( NSINSTALL) -L $( PWD) , $( NSINSTALL) -R)
2011-07-09 01:30:27 +04:00
2014-02-11 02:57:01 +04:00
e n d i f # WINNT
1998-03-28 05:44:41 +03:00
2012-07-03 10:43:30 +04:00
# The default for install_cmd is simply INSTALL
install_cmd ?= $( INSTALL) $( 1)
2002-04-25 06:52:44 +04:00
# Use nsinstall in copy mode to install files on the system
SYSINSTALL = $( NSINSTALL) -t
2012-07-03 10:43:30 +04:00
# This isn't necessarily true, just here
sysinstall_cmd = install_cmd
2003-08-15 01:36:22 +04:00
2004-11-30 02:14:13 +03:00
#
# Localization build automation
#
# Because you might wish to "make locales AB_CD=ab-CD", we don't hardcode
# MOZ_UI_LOCALE directly, but use an intermediate variable that can be
# overridden by the command line. (Besides, AB_CD is prettier).
AB_CD = $( MOZ_UI_LOCALE)
2018-02-20 23:28:21 +03:00
2018-02-28 15:16:17 +03:00
i n c l u d e $( MOZILLA_DIR ) / c o n f i g / A B _ r C D . m k
2018-02-20 23:28:21 +03:00
2014-08-01 20:53:05 +04:00
# Many locales directories want this definition.
2015-10-30 05:31:14 +03:00
ACDEFINES += -DAB_CD= $( AB_CD)
2005-01-26 16:33:53 +03:00
2008-07-22 10:57:07 +04:00
i f n d e f L 1 0 N B A S E D I R
2012-04-28 01:00:00 +04:00
L10NBASEDIR = $( error L10NBASEDIR not defined by configure)
2008-07-22 10:57:07 +04:00
e n d i f
2017-12-11 20:02:49 +03:00
EXPAND_LOCALE_SRCDIR = $( if $( filter en-US,$( AB_CD) ) ,$( LOCALE_TOPDIR) /$( 1) /en-US,$( or $( realpath $( L10NBASEDIR) ) ,$( abspath $( L10NBASEDIR) ) ) /$( AB_CD) /$( subst /locales,,$( 1) ) )
2005-01-26 16:33:53 +03:00
i f d e f r e l a t i v e s r c d i r
2017-12-11 20:02:49 +03:00
LOCALE_RELATIVEDIR ?= $( relativesrcdir)
e n d i f
i f d e f L O C A L E _ R E L A T I V E D I R
LOCALE_SRCDIR ?= $( call EXPAND_LOCALE_SRCDIR,$( LOCALE_RELATIVEDIR) )
2005-01-26 16:33:53 +03:00
e n d i f
2005-03-28 23:36:24 +04:00
2012-11-01 16:25:53 +04:00
i f d e f r e l a t i v e s r c d i r
2017-12-11 20:02:49 +03:00
MAKE_JARS_FLAGS += --relativesrcdir= $( LOCALE_RELATIVEDIR)
2012-11-01 16:25:53 +04:00
i f n e q ( e n - U S , $( AB_CD ) )
bug 1370506, always merge for l10n repacks, with internally set merge dir, r=glandium
To not merge the en-US language pack, the merge-% steps are in
a conditional function that disables that for en-US. Using a function
here as that's easier than a shell if in the merge rule, and
Makefile conditionals don't get evaluated late enough.
To liberate the l10n builds from settings in the automation,
we move the patch logic from LOCALE_MERGEDIR to REAL_LOCALE_MERGEDIR.
To determine strongly when we're in a repack or building a langpack,
the trick here is to
export IS_LANGUAGE_REPACK
in l10n.mk, and only set that to true in the entry-point rules.
Now, we can use that value in config.mk to define the l10n-specific
rules.
I did the same thing for langpack-%, which allows us to disable
the crashreporter files for language packs, for example.
With that,
make installers-de
just works, if you have localizations checked out.
For a while, we might run l10n-merge twice in automation, but it's really not
optional, so let's just make sure we run it.
MozReview-Commit-ID: 3nr33CKxkBQ
--HG--
extra : rebase_source : 0605a4adba018fa4b85d563cdafba80b0533bc91
2017-06-16 16:21:16 +03:00
i f d e f I S _ L A N G U A G E _ R E P A C K
MAKE_JARS_FLAGS += --locale-mergedir= $( REAL_LOCALE_MERGEDIR)
2008-10-20 23:57:47 +04:00
e n d i f
2012-11-01 16:25:53 +04:00
i f d e f I S _ L A N G U A G E _ R E P A C K
2012-11-03 20:13:56 +04:00
MAKE_JARS_FLAGS += --l10n-base= $( L10NBASEDIR) /$( AB_CD)
2005-06-01 15:59:09 +04:00
e n d i f
2012-11-01 16:25:53 +04:00
e l s e
MAKE_JARS_FLAGS += -c $( LOCALE_SRCDIR)
e n d i f # en-US
e l s e
MAKE_JARS_FLAGS += -c $( LOCALE_SRCDIR)
e n d i f # ! relativesrcdir
2005-06-01 15:59:09 +04:00
bug 1370506, always merge for l10n repacks, with internally set merge dir, r=glandium
To not merge the en-US language pack, the merge-% steps are in
a conditional function that disables that for en-US. Using a function
here as that's easier than a shell if in the merge rule, and
Makefile conditionals don't get evaluated late enough.
To liberate the l10n builds from settings in the automation,
we move the patch logic from LOCALE_MERGEDIR to REAL_LOCALE_MERGEDIR.
To determine strongly when we're in a repack or building a langpack,
the trick here is to
export IS_LANGUAGE_REPACK
in l10n.mk, and only set that to true in the entry-point rules.
Now, we can use that value in config.mk to define the l10n-specific
rules.
I did the same thing for langpack-%, which allows us to disable
the crashreporter files for language packs, for example.
With that,
make installers-de
just works, if you have localizations checked out.
For a while, we might run l10n-merge twice in automation, but it's really not
optional, so let's just make sure we run it.
MozReview-Commit-ID: 3nr33CKxkBQ
--HG--
extra : rebase_source : 0605a4adba018fa4b85d563cdafba80b0533bc91
2017-06-16 16:21:16 +03:00
i f d e f I S _ L A N G U A G E _ R E P A C K
2011-03-18 20:29:56 +03:00
MERGE_FILE = $( firstword \
2017-12-11 20:02:49 +03:00
$( wildcard $( REAL_LOCALE_MERGEDIR) /$( subst /locales,,$( LOCALE_RELATIVEDIR) ) /$( 1) ) \
2011-03-18 20:29:56 +03:00
$( wildcard $( LOCALE_SRCDIR) /$( 1) ) \
$( srcdir) /en-US/$( 1) )
Bug 1439742 - Allow {AB_CD} and {AB_rCD} in LOCALIZED_GENERATED_FILES. r=ted.mielczarek
There are a lot of choices and moving pieces in this commit. I elected
to include the mechanics and the target use case in the same commit so
that readers can compare and contrast the implementation and final
expression in one review window.
- Initially, I wanted to make the {AB_CD} substitutions in
LOCALIZED_FILES and not in LOCALIZED_GENERATED_FILES. However, I ran
into conceptual blockers doing this. Fundamentally, LOCALIZED_FILES
is FINAL_TARGET_FILES, and my use case should _not_ be putting files
anywhere near dist/bin. In addition, LOCALIZED_FILES
(FINAL_TARGET_FILES) is handled using manifests, which would need to
grow locale-aware functionality to handle this. That's not desirable.
In addition, if we use manifests, then we lose the powerful locality
of |mach build mobile/android{/base}| re-generating changed
locale-dependent resources. This is similar to how the build system
plumbs dist/idl manifest processing throughout the build: we're
repairing local workflows after moving work into a global process.
For these reasons, this doesn't support {AB_CD} in LOCALIZED_FILES.
- There is even another layer of complexity! There are two axes
involved with these files: AB_CD controls localization and the Make
target controls destination. For the record, it is:
regular builds - AB_CD unset
multi-locale builds - AB_CD set
single-locale repacks - AB_CD set
For the record, the existing logic (before any changes) is:
regular builds - Make target is `libs` in mobile/android/base/locales
multi-locale builds - Make target is `chrome-%` in mobile/android/base/locales
single-locale repacks - Make target is `libs` in mobile/android/base/locales
This commit adds targets for both destinations, and uses Make
chrome-%:: and libs:: magic to control what is invoked in the various
situations. Tricky!
- I added MERGE_RELATIVE_FILES in order to be able to follow-up this
patch with more patches that will get rid of
m/a/base/locales/{moz.build,Makefile.in} altogether, and fold this work
into m/a/base. As it stands, we're already reaching from
m/a/base/locales all the way out to
mobile/locales/.../region.properties, so the existing code doesn't
follow the layout expected between mozilla-central and
l10n-central/$(AB_CD). But that'll impedance will get worse as we
improve the build system dependencies, not better, so we should grow
support for localized resources that aren't exactly as expected.
- I chose to follow Python's syntax for string substitutions. I
would have preferred to mark files that should be localized with a
leading '%'... but I took that for filesystem absolute paths in
moz.build files already. I also considered @AB_CD@ to echo the
preprocessor, but didn't want to open the door to an expecation that
_all_ preprocessor DEFINEs will work in the way {AB_CD} does.
- The generate_*py script changes required a bit of a hack to "turn
off" locale dependent resources. This would have been nicer if we had
marked localized resources with '%'... but we didn't. See the
--fallback flag. The real reason this is needed is that we're doing
work which is more like the work of compare-locales (merging
locale-dependent resources) at build-time rather than repack time. I
don't know why that's the case -- probably when we (I) implemented it,
compare-locales and the whole l10n process was entirely opaque. It's
not worth changing it now, so we use this --fallback flag approach.
- I didn't get to tup support. This should gently fail without
breaking tup builds: any {AB_CD} substitutions just won't be
expanded. I haven't a clue how this should work in tup in the future
(or, more generally, how to make any sense of repacks without
declaring the full set of expected locales at configure time.)
- strings.xml can't be a LOCALIZED_PP_FILES, since we need to
customize the output location based on AB_rCD, and since we need a
little more flexibility than PP_FILES gives for our inputs.
MozReview-Commit-ID: MyfIkNSEzt
--HG--
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/en-US/localized-input => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/en-US/localized-input
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/foo-data => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/foo-data
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/generate-foo.py => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/generate-foo.py
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/en-US/localized-input => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/inner/locales/en-US/localized-input
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/moz.build => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/moz.build
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/non-localized-input => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/non-localized-input
extra : rebase_source : 816b6f220758f2bb3bdd3ec81a2cb02269c6de5b
2018-02-22 04:12:17 +03:00
# Like MERGE_FILE, but with the specified relative source directory
# $(2) replacing $(srcdir). It's expected that $(2) will include
# '/locales' but not '/locales/en-US'.
#
# MERGE_RELATIVE_FILE and MERGE_FILE could be -- ahem -- merged by
# making the second argument optional, but that expression makes for
# difficult to read Make.
MERGE_RELATIVE_FILE = $( firstword \
$( wildcard $( REAL_LOCALE_MERGEDIR) /$( subst /locales,,$( 2) ) /$( 1) ) \
$( wildcard $( call EXPAND_LOCALE_SRCDIR,$( 2) ) /$( 1) ) \
$( topsrcdir) /$( 2) /en-US/$( 1) )
2011-03-18 20:29:56 +03:00
e l s e
MERGE_FILE = $( LOCALE_SRCDIR) /$( 1)
Bug 1439742 - Allow {AB_CD} and {AB_rCD} in LOCALIZED_GENERATED_FILES. r=ted.mielczarek
There are a lot of choices and moving pieces in this commit. I elected
to include the mechanics and the target use case in the same commit so
that readers can compare and contrast the implementation and final
expression in one review window.
- Initially, I wanted to make the {AB_CD} substitutions in
LOCALIZED_FILES and not in LOCALIZED_GENERATED_FILES. However, I ran
into conceptual blockers doing this. Fundamentally, LOCALIZED_FILES
is FINAL_TARGET_FILES, and my use case should _not_ be putting files
anywhere near dist/bin. In addition, LOCALIZED_FILES
(FINAL_TARGET_FILES) is handled using manifests, which would need to
grow locale-aware functionality to handle this. That's not desirable.
In addition, if we use manifests, then we lose the powerful locality
of |mach build mobile/android{/base}| re-generating changed
locale-dependent resources. This is similar to how the build system
plumbs dist/idl manifest processing throughout the build: we're
repairing local workflows after moving work into a global process.
For these reasons, this doesn't support {AB_CD} in LOCALIZED_FILES.
- There is even another layer of complexity! There are two axes
involved with these files: AB_CD controls localization and the Make
target controls destination. For the record, it is:
regular builds - AB_CD unset
multi-locale builds - AB_CD set
single-locale repacks - AB_CD set
For the record, the existing logic (before any changes) is:
regular builds - Make target is `libs` in mobile/android/base/locales
multi-locale builds - Make target is `chrome-%` in mobile/android/base/locales
single-locale repacks - Make target is `libs` in mobile/android/base/locales
This commit adds targets for both destinations, and uses Make
chrome-%:: and libs:: magic to control what is invoked in the various
situations. Tricky!
- I added MERGE_RELATIVE_FILES in order to be able to follow-up this
patch with more patches that will get rid of
m/a/base/locales/{moz.build,Makefile.in} altogether, and fold this work
into m/a/base. As it stands, we're already reaching from
m/a/base/locales all the way out to
mobile/locales/.../region.properties, so the existing code doesn't
follow the layout expected between mozilla-central and
l10n-central/$(AB_CD). But that'll impedance will get worse as we
improve the build system dependencies, not better, so we should grow
support for localized resources that aren't exactly as expected.
- I chose to follow Python's syntax for string substitutions. I
would have preferred to mark files that should be localized with a
leading '%'... but I took that for filesystem absolute paths in
moz.build files already. I also considered @AB_CD@ to echo the
preprocessor, but didn't want to open the door to an expecation that
_all_ preprocessor DEFINEs will work in the way {AB_CD} does.
- The generate_*py script changes required a bit of a hack to "turn
off" locale dependent resources. This would have been nicer if we had
marked localized resources with '%'... but we didn't. See the
--fallback flag. The real reason this is needed is that we're doing
work which is more like the work of compare-locales (merging
locale-dependent resources) at build-time rather than repack time. I
don't know why that's the case -- probably when we (I) implemented it,
compare-locales and the whole l10n process was entirely opaque. It's
not worth changing it now, so we use this --fallback flag approach.
- I didn't get to tup support. This should gently fail without
breaking tup builds: any {AB_CD} substitutions just won't be
expanded. I haven't a clue how this should work in tup in the future
(or, more generally, how to make any sense of repacks without
declaring the full set of expected locales at configure time.)
- strings.xml can't be a LOCALIZED_PP_FILES, since we need to
customize the output location based on AB_rCD, and since we need a
little more flexibility than PP_FILES gives for our inputs.
MozReview-Commit-ID: MyfIkNSEzt
--HG--
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/en-US/localized-input => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/en-US/localized-input
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/foo-data => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/foo-data
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/generate-foo.py => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/generate-foo.py
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/en-US/localized-input => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/inner/locales/en-US/localized-input
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/moz.build => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/moz.build
rename : python/mozbuild/mozbuild/test/backend/data/localized-generated-files/non-localized-input => python/mozbuild/mozbuild/test/backend/data/localized-generated-files-AB_CD/non-localized-input
extra : rebase_source : 816b6f220758f2bb3bdd3ec81a2cb02269c6de5b
2018-02-22 04:12:17 +03:00
MERGE_RELATIVE_FILE = $( call EXPAND_LOCALE_SRCDIR,$( 2) ) /$( 1)
2011-03-18 20:29:56 +03:00
e n d i f
2014-12-17 18:06:14 +03:00
2010-03-24 02:24:38 +03:00
i f n e q ( W I N N T , $( OS_ARCH ) )
2015-11-13 12:23:24 +03:00
RUN_TEST_PROGRAM = $( DIST) /bin/run-mozilla.sh
2010-03-24 02:24:38 +03:00
e n d i f # ! WINNT
2009-03-02 09:28:09 +03:00
2005-12-18 20:09:28 +03:00
#
# Java macros
#
# Make sure any compiled classes work with at least JVM 1.4
JAVAC_FLAGS += -source 1.4
i f d e f M O Z _ D E B U G
JAVAC_FLAGS += -g
e n d i f
2008-12-19 17:50:24 +03:00
2014-11-30 04:45:31 +03:00
CREATE_PRECOMPLETE_CMD = $( PYTHON) $( abspath $( MOZILLA_DIR) /config/createprecomplete.py)
2011-04-13 04:27:41 +04:00
2012-08-27 23:27:16 +04:00
# MDDEPDIR is the subdirectory where dependency files are stored
MDDEPDIR := .deps
2015-07-07 12:29:12 +03:00
# $(call CHECK_SYMBOLS,lib,PREFIX,dep_name,test)
# Checks that the given `lib` doesn't contain dependency on symbols with a
# version starting with `PREFIX`_ and matching the `test`. `dep_name` is only
# used for the error message.
# `test` is an awk expression using the information in the variable `v` which
# contains a list of version items ([major, minor, ...]).
d e f i n e C H E C K _ S Y M B O L S
@ $( TOOLCHAIN_PREFIX ) r e a d e l f - s W $( 1) | \
a w k ' $$ 8 ~ / @ $( 2) _ / { \
split( $$ 8,a,"@" ) ; \
split( a[ 2] ,b,"_" ) ; \
split( b[ 2] ,v,"." ) ; \
if ( $( 4) ) { \
if ( !found) { \
2015-10-02 01:34:18 +03:00
print " TEST-UNEXPECTED-FAIL | check_stdcxx | We do not want these $( 3) symbol versions to be used: " \
2015-07-07 12:29:12 +03:00
} \
print " " ,$$ 8; \
found = 1 \
} \
} \
E N D { \
if ( found) { \
exit( 1) \
} \
} '
e n d e f
2013-07-31 09:04:23 +04:00
i f n e q ( , $( MOZ_LIBSTDCXX_TARGET_VERSION ) $( MOZ_LIBSTDCXX_HOST_VERSION ) )
2016-06-07 07:51:05 +03:00
CHECK_STDCXX = $( call CHECK_SYMBOLS,$( 1) ,GLIBCXX,libstdc++,v[ 1] > 3 || ( v[ 1] = = 3 && v[ 2] = = 4 && v[ 3] > 16) )
Bug 1278456 - Bump glibc requirement to 2.12. r=froydnj
The requirement for glibc has been set to version 2.7 for a long while.
Spidermonkey uses the pthread_setname_np symbol, which is only available
since glibc 2.12. So far, we've been fortunate that the symbol doesn't
end up in libxul, or tests that link to js directly, because the symbol
is eliminated as being called by effectively dead code.
There are multiple reasons why this is going to change, one of which
being changes to the way things are linked, that will make the linker
not eliminate that code in some cases. Another is that eventually, the
separation of build systems between js and top-level is going to fade,
and the glibc checks, which apply to all gecko binaries, will also apply
to js binaries. They currently are not happening, and would fail because
of pthread_setname_np if they were.
Taking a step back, as of version 46, the mozilla.org builds require at
least Gtk+3 3.4. Which means the requirements for the underlying system
have received a dramatic bump, and it's time to revisit the requirements
for binary compatibility.
I went through all my notes from all the recent times binary compatibility
has been considered, and put together a compatibility matrix on MDN from
that data as well as more recent data that I could find here and there,
about the major non-rolling-release distros (RHEL, Fedora, SuSE, Debian,
Ubuntu)
https://developer.mozilla.org/en-US/Firefox/Linux_compatibility_matrix
Considering the data there, none of the distros that have at least Gtk+3
3.4 have a glibc older than 2.13. The list of symbols that 2.13 provides
that 2.12 doesn't have is not large enough, though, to really care about
depending on 2.13.
2016-06-07 07:49:47 +03:00
CHECK_GLIBC = $( call CHECK_SYMBOLS,$( 1) ,GLIBC,libc,v[ 1] > 2 || ( v[ 1] = = 2 && v[ 2] > 12) )
2013-07-31 09:04:23 +04:00
e n d i f
2011-08-29 09:34:12 +04:00
2014-02-11 02:57:01 +04:00
i f e q ( , $( filter $ ( OS_TARGET ) ,WINNT Darwin ) )
2014-01-16 04:13:43 +04:00
CHECK_TEXTREL = @$( TOOLCHAIN_PREFIX) readelf -d $( 1) | grep TEXTREL > /dev/null && echo 'TEST-UNEXPECTED-FAIL | check_textrel | We do not want text relocations in libraries and programs' || true
e n d i f
2014-10-14 02:17:13 +04:00
i f e q ( $( MOZ_WIDGET_TOOLKIT ) , a n d r o i d )
# While this is very unlikely (libc being added by the compiler at the end
# of the linker command line), if libmozglue.so ends up after libc.so, all
# hell breaks loose, so better safe than sorry, and check it's actually the
# case.
CHECK_MOZGLUE_ORDER = @$( TOOLCHAIN_PREFIX) readelf -d $( 1) | grep NEEDED | awk '{ libs[$$NF] = ++n } END { if (libs["[libmozglue.so]"] && libs["[libc.so]"] < libs["[libmozglue.so]"]) { print "libmozglue.so must be linked before libc.so"; exit 1 } }'
e n d i f
2014-01-16 04:13:43 +04:00
d e f i n e C H E C K _ B I N A R Y
2015-07-07 12:29:12 +03:00
$( call CHECK_GLIBC ,$ ( 1) )
2014-01-16 04:13:43 +04:00
$( call CHECK_STDCXX ,$ ( 1) )
$( call CHECK_TEXTREL ,$ ( 1) )
2013-11-19 08:45:31 +04:00
$( call LOCAL_CHECKS ,$ ( 1) )
2014-10-14 02:17:13 +04:00
$( call CHECK_MOZGLUE_ORDER ,$ ( 1) )
2014-01-16 04:13:43 +04:00
e n d e f
2011-08-29 09:34:12 +04:00
# autoconf.mk sets OBJ_SUFFIX to an error to avoid use before including
# this file
OBJ_SUFFIX := $( _OBJ_SUFFIX)
# PGO builds with GCC build objects with instrumentation in a first pass,
# then objects optimized, without instrumentation, in a second pass. If
2014-03-03 01:35:24 +04:00
# we overwrite the objects from the first pass with those from the second,
2011-08-29 09:34:12 +04:00
# we end up not getting instrumentation data for better optimization on
# incremental builds. As a consequence, we use a different object suffix
# for the first pass.
i f n d e f N O _ P R O F I L E _ G U I D E D _ O P T I M I Z E
i f d e f M O Z _ P R O F I L E _ G E N E R A T E
i f d e f G N U _ C C
OBJ_SUFFIX := i_o
e n d i f
e n d i f
e n d i f
2012-02-13 18:48:23 +04:00
2014-11-30 04:45:31 +03:00
PLY_INCLUDE = -I$( MOZILLA_DIR) /other-licenses/ply
2012-06-20 11:00:48 +04:00
export CL_INCLUDES_PREFIX
2017-02-22 08:22:01 +03:00
# Make sure that the build system can handle non-ASCII characters
# in environment variables to prevent it from breking silently on
# non-English systems.
export NONASCII