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
Also update the configure to use MOZ_APP_VERSION for MOZ_APP_VERSION_ABOUT
if not found
--HG--
extra : rebase_source : bf511748c78577a2b84465bf4798ee635b036c22
A single file with two lines was breaking too much things
---
browser/config/version.txt | 2 --
browser/config/version_about.txt | 1 +
configure.in | 4 ++--
3 files changed, 3 insertions(+), 4 deletions(-)
create mode 100644 browser/config/version_about.txt
This should not have any effect on nightly or aurora.
Also fix browser/installer/windows/Makefile.in
webapprt/win/Makefile.in to use the variable instead
of the file
CLOSED TREE IGNORE IDL
--HG--
extra : rebase_source : 97a096424b43fc4bed692182841843131fdcee13
extra : histedit_source : 4754300927dac90f0ae879e90896e36f1aa28b49
