When we build universal binaries, we effectively cross-compile
from 64 to 32 bit darwin. Check for this and add the appropriate
target triplet to the definition of RUSTC.
Move the MacOS X 10.6 linkage check to after HAVE_64BIT_BUILD is defined.
This patch introduces a background service for downloading content from a
catalog (bug 1200291). This catalog ships with the application and contains
only fonts in this first version (MOZ_ANDROID_EXCLUDE_FONTS).
For now this service is disabled by default (MOZ_ANDROID_DOWNLOAD_CONTENT_SERVICE).
--HG--
extra : commitid : 7v0q886zR9q
extra : rebase_source : cf877b0ab7d286d1f973daebc8c004b320e426c7
For build speed, for correct line numbers in errors, for faster development, for so many reasons.
Still a couple of cases left mostly in XUL files for different strings on Windows.
Bonus: The new lexical scope means ADDON_SIGNING and REQUIRE_SIGNING can just
be declared as regular constants and outside code can't get to them easily.
--HG--
extra : commitid : Kj8khjuCwG2
extra : rebase_source : 2e0a3143900c0c414cda43254306f0c070f8e621
PKG_CHECK_MODULES sets the values, and AC_SUBST_LISTs them on its own.
No need to duplicate the values to variables local to configure.in to
then AC_SUBST/AC_SUBST_LIST them. Also, since bug 1224452, MOZ_PIXMAN_CFLAGS
needs to be an AC_SUBST_LIST instead of AC_SUBST.
We're going to change how e.g. CFLAGS are printed out in backend.mk, and
to fit that model, the data in the corresponding moz.build variables
need to be straightened up.
This patch moves the logic for selecting MOZ_WINCONSOLE out of individual
Makefile.in files and into configure. It also changes config.mk to only
pass -SUBSYSTEM:CONSOLE if MOZ_WINCONSOLE=1. The MSDN docs state that
in the absence of -SUBSYSTEM, the linker will select the proper subsystem
based on whether the program contains [w]main or [w]WinMain, so let it
do that.
One program (windbgdlg) needed a tweak to add a wmain for when MOZ_WINCONSOLE
is defined.
This patch leaves one instance in security/sandbox/win/wow_helper/Makefile.in,
that Makefile has its own separate bug.
--HG--
extra : commitid : 8acDjmfKivj
extra : rebase_source : 03b4fa4c8ae077a894b08f3762ef93541e34ac1a
Dehydra/Treehydra is unmaintained, broken (iirc), and obsoleted by clang
static analysis. We've removed parts of the build system support for it, but
not all. This is meant to remove the remains.
We're going to be using -I$_topsrcdir in some CFLAGS variables, and for that
we need windows-y paths, not msys paths. All things currently using
$_topsrcdir should cope with this just fine.
Add a switch to enable the rust mp4parser code through confvars.sh
and set this for browser targets. Configure will only pass this
through as a CPP define if the rust toolchain is available.
The MOZ_RUST check is hoisted to an outer conditional to
make it cleaner to add other features.
Thanks to zhoubcfan@163.com for the typo fix in configure.in.
Add a switch to enable the rust mp4parser code through confvars.sh
and set this for browser targets. Configure will only pass this
through as a CPP define if the rust toolchain is available.
The MOZ_RUST check it hoisted to an ourter conditional to
make it easier to add other features.
webtrc should be used on aarch64 targets. When not enabled we hit
bad ANDROID_NDK path (see Bug 1218702) so we actually cannot build
without it right now.
Since MOZ_NATIVE_DEVICES builds against play-services-{basement,base,cast},
some ad-hoc de-duplication is necessary.
--HG--
extra : commitid : 2jNIgZpLUq2
extra : source : 0957d3435ac22765d7868cb3c7db1e0787836bc3
These flags are not intended to be feature specific. On day one, we
intend to support a single GCM-backed feature -- Push Notifications --
but the set of GCM-consuming features is potentially large (e.g.,
possibly Firefox Sync tickles and Send Tab to Device alerts). Such
features can and will have their own build flags.
Note that GCM sender IDs are not sensitive -- see link in code
comment. Since this is something custom branding will almost always
want to set, I don't want to bury the default value in confvars.sh.
--HG--
extra : commitid : HBHDBk2tC6S
extra : source : d4e39587c87c16564eeac6d1f8568814b63e5325
A new configure option --with-devtools (which sets MOZ_DEVTOOLS) is added to
control whether all DevTools, just the server, or no DevTools are included.
This defaults to just the server.
Applications should also include /devtools within their moz.build tree, so that
DIST_SUBDIR is in effect for all DevTools files if it is used by the app.
In bug 922912, we folded back gkmedias.dll info xul.dll, so in practice, there
is no default configuration left that exercises GKMEDIAS_SHARED_LIBRARY. And
sure enough, it's been broken for months in many different ways.
The gkmedias intermediate library is however kept for webrtc signaling tests.
The configure option has explicitly thrown an error for more than a year now,
and it happens that the remaining way to still forcefully use it has been
broken for more than 8 months.
The flags added in toolkit/locales/Makefile.in turn out not to be actually
used, so just remove that.
The remaining uses of XULPPFLAGS are to set debug flags depending on whether
MOZ_DEBUG is set or not. Just set a dedicated variable with the right value
from configure.
The order in which backends appear is important, and dealing with deduplication
in configure.in is not really nice, so for all simplification purposes, this relies
on using AC_SUBST_SET, which does the deduplication and keeps the original order
in which items appear (despite its name).
As of MSVC2012 this warning no longer occurs, because the code pattern it's for
is valid C++11, so we no longer need to disable the warning.
This undoes bug 832280.
--HG--
extra : rebase_source : e38a414ef134d0ffd0aadde697a18eedb46bf849
Right now, --with-android-sdk expects a path to a specific Android SDK
version, like /path/to/platforms/android-22. That path is exposed as
ANDROID_SDK; the Android SDK root is exposed as ANDROID_SDK_ROOT.
Right now, the provided platform's version number is extracted into
ANDROID_TARGET_SDK. The extracted ANDROID_TARGET_SDK is checked
against a minimum version number (supplied as a parameter to
MOZ_ANDROID_SDK).
After this patch, --with-android-sdk expects what is now
ANDROID_SDK_ROOT, and then derives ANDROID_SDK from that path and a
pinned SDK platform version number. The exact version number which we
search for is now a parameter given to MOZ_ANDROID_SDK. We accept and
fail, with a helpful message, if we recognize an old-style ANDROID_SDK
path.
The existing MOZ_ANDROID_{MIN,MAX}_SDK_VERSION variables remain as
they are.
Right now, the Android build tools are searched in a deterministic but
non-obvious manner. After this patch, the exact build tools version
number is now a parameter given to MOZ_ANDROID_SDK.
--HG--
extra : commitid : 7z4T3EYH8fg
extra : rebase_source : 118a2a163d0deb1896e4959f12e9fbb132732bd8
extra : histedit_source : f18feda343e3c8e9f0dbb65eb7127262690e3cad
This patch allows you to set MOZ_APP_ANDROID_VERSION_CODE in a branding's configure.sh to specify the exact android:versionCode to use in the final (main) APK. It does *not* modify the android:versionCode used in any other APKs.
--HG--
extra : transplant_source : U%F31E%1AK%3BY%18e.%E8%BD%F3_0%04%C6%84%7B
As part of this move, HOST_NSPR_MDCPUCFG needed to be changed to get the quoting right.
--HG--
extra : commitid : J26MhSiPq9g
extra : rebase_source : 81c5b98371042803741ddace8d01b0097757dff3
Even though we compile C code as C99, we used to need
-Wdeclaration-after-statement because MSVC didn't allow declarations after
statements.
However, Visual Studio 2013 added support, so we can now merrily mix
declarations and statements everywhere. Hooray.
--HG--
extra : rebase_source : 00a89fed733008785429827408a0c6c466971080
This warning is typically triggered by code which implements
some kind of assertion macro, and it's probably not a good
indicator of bugs anyway, so there is no good reason to keep
it on.
Currently, all versions of Firefox run with the existing native
Firefox Account UI. This flag will opt-in to maintaining that
experience while we transition to a web account UI. Once we're stable
on the web, we'll remove this flag entirely.
--HG--
extra : commitid : CmokCKcYNJQ
extra : rebase_source : eb7e8f136f9a5134f84c8dbe111841b72827146a
The PR was fixed in early 2011. clang 3.3, the oldest version of clang
that we build with, was released in mid-2013. It's safe to say that all
versions of clang now have this fix, and we can delete the check.
qcms and libav use __attribute__((force_align_arg_pointer))
unconditionally; the libav use case suggests that the attribute has been
around since GCC 4.2. We're well past that point with GCC, and clang
supports it also. So we can simply assume the compiler has it in the
appropriate places.
It is, however, x86 only (x86-64 appropriately aligns the stack at all
times), so we need to adjust the libpixman build code appropriately.
<sys/int_types.h> appears to be a pre-standardization header that was
common on SunOS systems (which apparently also provided <inttypes.h>?).
Searching also turns up references in the NetBSD source tree for
less-common architectures (e.g. sh3). There are a few includes for
<sys/int_types.h> in the tree, but only as a fallback for <inttypes.h>.
In short, we don't care about this header, and we shouldn't check for it.
We appear to be inconsistent about which CFLAGS variables get
substituted as lists (most things relating to widget libraries, for
instance) and which are just raw strings (most everything else). This
patch is a first step towards making everything a list, which makes the
next patch much easier to write. The other variables can be converted
as a followup bug.
Bluedroid's HAL backend has been superseded by the Bluetooth daemon, and
already been unused in current releases. This patch removes the code from
Gecko.
Optimised Rust compilation is enabled on passing --enable-optimize to
the configure script. This sets the RUSTFLAGS output variable that gets
picked up by the compile targets RSOBJS and RSSRCS and passed to rustc.
r=glandium
--HG--
extra : commitid : 8thSkfLFXSY
extra : rebase_source : 5ec79b76a187bcbb0f09ad374cf9f763f0adb0d7
By default the rust standard library uses linker-assisted
thread-local storage, which isn't supported on MacOS X 10.6.
If we're targetting that version make sure we can link code
built with $RUSTC.
If so it's presumedly been built with alternate support.
libvpx dropped vpx_mem_set_functions,
only use it if an external libvpx
is used and still has it.
update update.py
add vpx_dsp_rtcd.h
rebase disable_pthread_on_mingw.patch
add vp9_filter_restore_aligment.patch
drop msvc2015.patch
If we don't want this for rustc, we shouldn't have it for
other tools. Note that setting absolute paths will still
work, but relative ones won't.
--HG--
extra : rebase_source : f6995f76348052909079425aa5351d073053b8ab
Ralph Giles
Carsten "Tomcat" Book
Sebastian Kaspari
Chris Peterson
Nick Alexander
Mike Hommey
Kit Cambridge
Dave Townsend
Kalpesh Krishna
Randall Barker
Ted Mielczarek
Glenn Randers-Pehrson
Sotaro Ikeda
Sylvestre Ledru
Phil Ringnalda
Jon Coppeard
Eric Rahm
Wes Kocher
Adam Farden
James Willcox
Joel Maher
Jonathan Almeida [:jonalmeida]
J. Ryan Stinnett
Ryan VanderMeulen
Fabrice Desré
Iaroslav (yarik) Sheptykin
Kai Engert
Karl Tomlinson
Jacek Caban
Steve Fink
Terrence Cole
Justin Dolske
Kevin Grandon
Nicholas Nethercote
Eitan Isaacson
Nathan Toone
Ehsan Akhgari
Nigel Babu
Jordan Lund
Mark Finkle
Makoto Kato
David Major
Nathan Froyd
James Long
Bas Schouten
Lee Salzman
Thomas Zimmermann
Giovanny Andres Gongora Granada
ISHIKAWA, Chiaki
Andreas Tolfsen
Jed Davis
Sylvestre Ledru
Kyle Machulis
Valentin Gosu
Jan Gerber